All the processes are idle, so it's not really an issue.
The fact that it's still a process is the issue. If it's not doing something, I
don't want it running, taking up space.
There is (intentionally) a persistent pool of sqwebmaild processes; you can
change the SQWEBMAIL_PREFORK setting in the sqwebmaild config file if you
want to change the number of processes.
The ispell processes, however, should not be sitting around. Perhaps
sqwebmaild forgot to close its end of the pipes (when they tried to write,
they should have got a SIGPIPE signal). Or perhaps it doesn't leave the
signal handlers in the correct state when it exec's ispell.
Sam?
No, that can't happen. After servicing the request the sqwebmaild process
terminates, taking down all file descriptors with it.
That's what I was thinking. What's the best way to go about debugging this? I've
only seen it happen for this one user, and I've seen this same situation
repeated a few days later. It may have happened before, but just not noticed it.
Thanks for the responses,
!tr
28 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] stale processes and m17n
