However, now I have two running processes in addition to the supervise process. One is tmda-ofmipd running as vmail which is what should be there. The other process seems to be the root process used to spawn tmda-ofmipd. It isn't exiting properly. This symptom is, in fact, what prompted me to write the -D patch in the first place.
Here is the run script I'm using now.
#!/bin/sh
exec su - vmail -c "/usr/bin/tmda-ofmipd \
-A '/usr/local/sbin/courierpasswd -s imap --stdin /bin/true' \
-c /home/vmail"
And here are the two processes that are running.
root 4920 0.0 0.2 4080 1396 ? S 19:10 0:00 su - vmail -c /usr/bin/tmda-ofmipd -A '/usr/local/sbi
vmail 4924 0.0 0.5 5152 3592 ? S 19:10 0:00 /usr/bin/python /usr/bin/tmda-ofmipd -A /usr/local/sbin/courierpasswd
I don't know if having this root process hanging around is of any consequence but that's the point in my opinion. If I don't know, I'd rather it wasn't there.
Andrew
Andrew wrote:
Apparantly, it doesn't. I just tried running tmda-ofmipd from a supervise run script two different ways:
1. without the fgcheck program and without the -D option
2. with both the fgcheck program and with the -D option
Neither worked. In the first case, supervise began to spin as soon as I started it. Tmda-ofmipd would immediately die for some reason and supervise would start a new process. In the second case, supervise could not successfully start tmda-ofmipd at all.
These were just quick tests so this may not be the final word on the subject. If someone else is able to get tmda-ofmipd to work with supervise, I would be interested to know how they did it.
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
