[EMAIL PROTECTED] wrote:
> With previous versions, I have been using the old standard of
> using a tcpserver run file for qpsmtpd and logging, and an init.d file for
> starting, stopping, and otherwise managing qpsmtpd via tcpserver commands.
I'm assuming that your init.d script contains the equivalent of:
stop: svc -d
start: svc -u
or some such. That will work fine with forkserver as well, since the parent
process is still managed with svscan, or are you not even running svscan (and
for G-d's sake why not!).
> How are you starting the run file(s)? How are you getting
> qpsmtpd-forkserver to recognize changes to plugins? How are you stopping,
> restarting, etc.?
# svc -t
will restart qpsmtpd and reload plugins. I suppose we could add a signal
handler to notice SIG_ARLM and reload the plugins, but I hardly see the point.
John
