On Sat, 14 Jan 2006, John Peacock wrote:
> [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.
Clearly, to me, that I don't fully understand tcpserver and the
svc commands. I was under the impression that if you set things up with
the service directory and such, that it would invoke a new qpsmtpd (or in
this case, qpsmtpd-forkserver) for each connection. Obviously, we don't
want the latter.
But to answer your question - yes, my current init.d script does
use the svc command for just about everything. So if you are telling me
that it will work properly (pretty much as is), then I'll give it a try
(after converting all of my "too customized" plugins to be less so).
Thanks.
