Hello, Am Samstag, 4. August 2018, 00:11:02 CEST schrieb David Haller:
On Fri, 03 Aug 2018, Michael Ströder wrote:
On 08/03/2018 08:40 PM, David Haller wrote:
Let's see what our then ML-Admin had to say about that a while ago and why the lists are run with mlmmj:
==== Wenn diese Liste über Mailman betrieben würde, dann würden wir den ganzen Tag nichts anderes machen als eine Menschenkette zum nächsten Computerladen aufrechtzuerhalten um RAM in einem konstanten fluss in lists.suse.com einzubauen ;) -- suse-linux-owner, ebenda ==== If this list were run with mailman, we'd have to have a chain-of-people to the next computer-store all day to install a constant stream of RAM into lists.suse.com ;) ====
Could you please elaborate on what "a while ago" really means?
Oh, dunno, it's been quite a while I guess. In the naughties. Probably the first half... ;)
# grepsig mailman % Wenn diese Liste über Mailman betrieben würde, dann würden wir den ganzen Tag nichts anderes machen als eine Menschenkette zum nächsten Computerladen aufrechtzuerhalten um RAM in einem konstanten fluss in lists.suse.com einzubauen ;) [Henne Vogelsang in suse-linux] ###cb### 2003-05-30 % Looks like it was a good idea to add timestamps to my signature collection ;-) If someone is interested in the context, the original mail is https://lists.opensuse.org/opensuse-de/2003-05/msg04486.html
(BTW: Does mlmmj sill receive good security reviews? Or at least are decent AppArmor profiles in place?)
No idea about AppArmour[-1]
Lovely typo, but please s/ur/r/ ;-) We have AppArmor profiles in place for mlmmj - I know that because I helped Per with a few small profile adjustments a while ago. These profiles are even packaged, but not enabled by default on "normal" installations. The few people who need them / use mlmmj can simply cp $(rpm -ql apparmor-profiles |grep mlmmj) /etc/apparmor.d/ and will get exactly the same profiles that are in use on lists.o.o ;-)
Mailman _WAS_ considered and (obviously, because of it's need of RAM) rather fast discarded as an alternative... And I very much doubt the actual list-server has anything to do with the "problem", it rather is the WUI (Web-User-Interface) to the _ARCHIVE_ of the list that is the problem. And mlmmj has nothing to do with that. Nor had ezmlm.
Just as a sidenote (and without having read the full discussion yet) - our current list-owner (Per) thinks about switching to mailman (after testing etc.). AFAIK the usual ENOTIME is delaying this. I don't know if switching to mailman would also mean to change our mailinglist archive because (at least currently) it's completely independent from the mailinglist software. Personally, I run a few lists/newsletters with mailman (the biggest is a newsletter with about 2k subscribers IIRC, but only two mails per month). These lists are not big enough to cause serious load and/or RAM usage on the servers you can rent nowadays ;-) I probably don't need to mention that lists.o.o has more traffic.
-dnh, "Memory fault -- core...uh...um...core... Oh dammit, I forget!"
No worries, my sigmonster will remember ;-)
[-1] Bcc-ing the AppArmor guru too
That's a new title (thanks!) - usually the other AppArmor developers call me "a devs walking nightmare" ;-) Regards, Christian Boltz PS: non-random signature -- * cboltz wonders if jjohansen already regrets calling me "a devs walking nightmare" <jjohansen> cboltz: no it still fits :P [from #apparmor] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org