Hello,
I've experimented this kind of behavior :
the client was not able to respond (or maybe very slowly) so processes on
the server were idle (expecting data, but no timeout) and the group was
considered 'running'.
I've stopped the group, but on the client, networker maintains lock files
(normally deleted after a successfull save) to prevent group from being
launched a second time when running . This files are under /nsr/tmp/, named
<group-name>.lck
So, killing processes on the client (or on the server) may not be sufficient
to enable again the group launching (especially if there is no connection
between server and client). You have to check for that .lck files and delete
them if necessary... after further investigation, of course !
Denis
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|