Clemens, > first of: if you want timestamps then integrate the last two lines from > > | $setuidgid qmaill $tai64n 2>&1 \ > > | $setuidgid qmaill $multilog /var/log/pop3d & > > to > | $setuidgid qmaill $multilog t /var/log/pop3d & Thanks for pointing this out! Should have noticed this. It's pointed out at http://cr.yp.to/daemontools/multilog.html! > also, if you tell qmail-pop3d to output stderr on the stdout stream with > the term "2>&1", telnet will give you error messages from pop3d too. if > you leave out this term, you get separate output and error streams. I am afraid that I would disagree with the above statements. After some more tinkering last night (what a wonderful way of killing a nice Friday evening!), I have come to the conclusion that tcpserver must be doing something that might be affecting IO redirection of qmail-pop3d. If you take out the 2>&1, your tcpserver will write its info msgs to console. In addition, the qmail-pop3d will still spit its output to STDERR to POP clients. Please try it and you will see for yourself. I just did (again, did once last night already). I will review both the src of both tcpserver and perhaps qmail-popup in this weekend, and see if I can catch the cause. In a follow up to my previous post, Russ Allbury ([EMAIL PROTECTED]) mentioned that QUALCOMM's qpoper does the kind of logging I am looking for. I took a look of qpoper's src, and immediately consider it a can of worms :> To me, qmail-pop3d is much compact and cleaner. I will patch it so it does logging that betters qpopper. Thanks for your feedback. Regards, Chin Fang [EMAIL PROTECTED] > -- > clemens [EMAIL PROTECTED] >
