Hi Chris,
I think I found the problem with the signalling -- it looks like the
call to kill_proc() is incorrect. It doesn't set the priv flag, so it
may fail to send a signal depending on which process and/or user is
making the call. I'm always running as root so I don't see any failures,
but probably if the connection fails for a user task the signal won't be
sent.
Hmm.. could be.
ls -l <directory> failed when not as root (just -32 and a timed out, try
again message), but then as root I get a similar message followed by a
connect and things work...
Does this fit the pattern of failures you're seeing? I'll get it fixed
right away ..
Could be. I'll alter the code and get back to as to whether this works.
-Chris