On Fri, 22 May 2009, Charlie Brady wrote:
On Fri, 22 May 2009, J wrote:
However, I'm back to seeing the connection processes being left behind,
despite an explicit quit from the remote host. I suspect this is due to
not using a queueing plugin, at this point.
I also see that 'svc -d' lea
On Fri, 22 May 2009, J wrote:
My current 'run' file (posted in previous message(s)):
=
#!/bin/sh
exec 2>&1 \
No, that's not what you have. You've deleted the trailing backslash,
right?
sh -c '
exec \
/usr/local/bin/softlimit -m 1
On Sat, 23 May 2009, Charlie Brady wrote:
> It looks to me as though qpsmtpd should have started a new process group with
> the parent process, but hasn't. Or the developer assumed that qpsmtpd would be
> set up as leader of a process group, but it isn't in this circumstance.
>
> Try this as your
On Sat, 23 May 2009, Charlie Brady wrote:
> On Sat, 23 May 2009, J wrote:
>
> > A manual connection where I connect, helo, then quit - stays in the
> > process table.
>
> If you strace that process, you'll see that it goes back to select() waiting
> for a new connection on the socket. You should e
On Sat, 23 May 2009, J wrote:
A manual connection where I connect, helo, then quit - stays in the
process table.
If you strace that process, you'll see that it goes back to select()
waiting for a new connection on the socket. You should expect each child
process to be reused up to 100 times
