On Monday, Feb 23, 2004, at 16:09 US/Mountain, Jason R. Mastaler wrote:
Jeff Ross <[EMAIL PROTECTED]> writes:
One other caveat...although tmda-ofmipd seems to run okay under daemontools, sending a svc -d to /service/tmda-ofmipd will not cause the daemon to go down. Instead, svstat /service/tmda-ofmipd will report that the service is up but wants down, and that's where it stays. svc -t seems also not to work as it should. In fact, in my limited testing so far, I found the easiest way to have tmda-ofmipd run with different flags (i.e., -d or not) was to reboot.
daemontools is an extremely weird piece of software. I stopped using it years ago when I finally got fed up with its unpredictable behavior. Even with djb's own tools like qmail, svc -t/-d would frequently not work correctly (this was on FreeBSD).
Never had any trouble with qmail at all...sometimes there is a slight delay while qmail-send tries to flush the queue, but other that that (and I think that is probably the correct behavior), daemontools and qmail work fine together for me. Ditto for sshd, dhcpd, wnsd, socklog, and all of the other daemon-ized software I run on my servers here.
Anyway, my recommendation is to only run tmda-ofmipd under daemontools if absolutely necessary. On my Debian system, a simple 30-line shell script in /etc/init.d/ with start/stop/restart cases manages tmda-ofmipd flawlessly, plus it's much easier to understand and debug.
So, for those of us that don't use /etc/init.d, we do...what? Switch to linux?
I'm not trying to start a pissing contest, here. In fact, I will not respond to anyone that reads this as such and responds with a "My A OS is better than your B OS, and here's why!", so let's not even start that, please.
I do linux at work. I won't run it on any of the openvistas.net servers.
If you reference my earlier messages in this thread, remember that I was unable to start tmda-ofmipd from /etc/rc.local on my OpenBSD system. First I was getting an "env" error, which I thought I'd solved by specifying the full path to Python. Even then, though, and even though it seemed that tmda-ofmipd was up and running, it would not work--i.e., it was failing to listen to port 8025, even thought that port was specified in the rc.local script.
My solution outside of using daemontools was to start the tmda-ofmipd daemon by hand after each reboot. My UPS is a big sucker, but I can't always guarantee that I'll be here when the power is out long enough that the UPS shuts the system down. Or that I'll notice when, for whatever reason, tmda-ofmipd crashes, like it was doing when it hit that 50MB area of ram usage.
I can live with not having svc -d or svc -t. I really do have to have the ability to bring up a working daemon at a reboot, and I really do have to have a restart of the daemon in case tmda-ofmipd crashes. My customers expect no less. E-mail is, as we all know, "just supposed to work".
If they only knew what we are doing behind the scenes to make sure that their precious multi-forwarded many times, virus-laden, worthless to all but them, stupid joke e-mail costs in real terms ;-)
Jason, I will thank you again for being the inspiration and the team leader of the TMDA project. tmda-ofmipd may need a little tweaking ;-), but I know that my virtually spam and virus free customers are damned glad that I've chosen to use TMDA on mail.openvistas.net.
And, as someone with 1000+ messages in pending, I'll second that!
Jeff
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
-- Jeff Ross Open Vistas Networking, Inc. http://www.openvistas.net _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
