/Networker [|] Magnus Naeslund
PGP Key: http://www.genline.nu/mag_pgp.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I run a relatively low traffic mailserver.
It runs qmail smptd and pop3 from inetd.
I hear all the time that inetd sucks, but i never hear any reasons why.
So my question is: why does inetd sucks?
/Magnus Näslund
Okay, i guess you all wanna hear success stories?
Well i got one for ya!
Before:
Using syslog/splogger.
50 in concurrencyremote.
I do a "killall -ALRM qmail-send".
Syslog was at >80%, mostly kernel time.
Not counting qmail daemons CPU%.
Load was at worst ~3.50.
The box was kinda crawling (that me
ake like 25/7days/24 hours i get around 150KB logging per hour.
That does not justify a 80% load of my system on syslogd's behalf...
Does anyone recognize this, or even better have a solution?
Any tip at all is super-welcome :)
/Magnus Naeslund
Why does not qmail transfer the control for *@skywalker.nu to the
skywalker.nu user?
The mails get caught in ~/alias/qmail-default
Any ideas?
/Magnus Naeslund
I had a fully working qmail system, but thought that the TLS patch on
qmail.org would be really nice to have.
Once i applied the patch my qmail-remote started to crash.
As soon as i reversed the patch, it worked as usual.
Have anyone else experienced this?
Cheers
Magnus Naeslund
