"Chris Berry" <[EMAIL PROTECTED]> writes: > >From: Tim Legant <[EMAIL PROTECTED]> > >"Chris Berry" <[EMAIL PROTECTED]> writes: > > > Ok I went back and implemented it as root > > > > > > /usr/local/src/tmda-0.81/bin/tmda-ofmipd -S > > > /usr/local/src/vmailmgr-vdir.sh -u root > > > >Just a note... you don't need the -u flag at all, if you run it as > >root. > > When I tried that I got an error saying that it expected the tofmipd > user or something of that sort, and the docs said that it tries to > default to that. I can try to recreate the message if you want to > take a look at it.
No, you're absolutely correct. I did the vpopmail and vmailmgr support simultaneously and I still confuse myself sometimes about which one works in which fashion. > > > Now I'm working on getting > > > it running under daemontools. > > Here is what I did: > > mkdir /var/log/qmail/tmda-ofmipd > mkdir -p /var/qmail/supervise/tmda-ofmipd/log > chmod +t /var/qmail/supervise/tmda-ofmipd > > tmda-ofmipd run script > #!/bin/sh > exec /usr/local/src/tmda-0.81/bin/tmda-ofmipd -f -S > > /usr/local/src/vmailmgr-vdir.sh -u root > > tmda-ofmipd log run script > #!/bin/sh > exec /usr/local/bin/multilog t /var/log/qmail/tmda-ofmipd > > then I chmod 755 both scripts and switched to the /service directory > > ln -s /var/qmail/supervise/tmda-ofmipd tmda-ofmipd Looks good. > Out of curiousity, why did you decide to /dev/null the errors rather > than log them? The messages output by tmda-ofmipd can be roughly broken down into three categories. First are messages that are printed before the server starts accepting connections, either because you asked for the information (-V, --version) or because of a misconfiguration; e.g. /etc/tofmipd isn't owned by root when you run tmda-ofmipd as root. Once tmda-ofmipd is working in the foreground, not supervised, these messages won't show up again. Second are messages printed when a catastrophic error occurs (a Python exception is thrown). Sometimes these occur because of configuration errors, also. I never had one of these thrown during my testing time of actual use, only while I was doing development on tmda-ofmipd. Finally, during regular execution of the server, numerous messages are printed for each connection, but only if you use the -d/--debug switch. I don't, so these also never get printed. In several months of operation, the only message tmda-ofmipd ever produced (for me) was the initial warning about running as root. So, when I put it under supervise, I didn't bother with logging. I didn't mean to suggest that you shouldn't log; in fact, you may prefer to run with the -d flag, just to track connections, if you run a fairly busy site and expect to do a lot of support. Also, if you do run into problems with the vmailmgr support, the logging output will be of value to me in trying to figure out what went wrong. ;) Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
