> I'm new to this group and am so relieved to find it.  I've been using
> Networker for only about a year and a half now so please bear with me if I
> ask stupid questions.  Here is my first one. :)
> 
> I have a backup group defined that has two clients associated to it.  One
> client is for a filesystem on the server itself and the other is for a
> filesystem on a remote client.  Now I'd like to run a post processing script
> via savpnpc on the server's client but only when the remote client has
> finished backing up its filesystem (the servers fs finishes in a mater of
> minutes and the remote can take a few hours).

'savepnpc' is a simple per-client interface for start/stop scripts.
There's no way that I'm aware of to ask it for dependencies between
clients.

Workarounds that I can think of, in no particular order:

Put clients into separate groups.  Rather than using the Networker
scheduler, fire them sequentially from a script.  After the client group
finishes, run the server group.

Make the script fired by savepnpc more powerful.  As it runs, have it
contact the server to run the finish script there.

Have something on the server or the backup server that polls the status
of the client backup.  When it sees that backup complete, it runs the
post-backup job on the server.

Turn the savegroup parallelism in your group way down so that only one
client is running at a time.  Then set the priority so that it runs the
client first.  It'll run the server after.  However, that means that any
savepnpc start job on the server would run after the client finished.
That may not be suitable for you.

> Currently we have a number of servers set up in this exact same fashion that
> work great but I just set up two new groups on two different servers and
> they both ran their savpnpc's post client script on the server when the
> server's client finished (it did not wait for the other client to finish).
> Am I doing something blindingly wrong here?  Am I providing enough
> information?

Savepnpc should be per-client.  There's no correlation between clients.
I'm not sure what's going on if your other groups appear to have
dependencies between the clients.

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

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