George Sinclair wrote:

I have come
to the conclusion that when backing up 2 or more pathnames, it will be
necessary to run each one separately, or if running from a script, then
simply loop through the save command for each desired pathname. This is
more time consuming because it will not be multiplexing, but at least it
works. Alternatively, I guess each save could be launched as a separate
process.

As Byron pointed out, you will need each of these run as a separate
command. 1 save = 1 SSID. If there aren't too many of them, you could
loop round the list and kick each save off in the background. This is
easy in sh, and you can put a wait command after the loop. However I
wouldn't recommend this approach if there are more than a handful of
save sets to backup, then you would need some more complex code to limit
the number of saves you are running simultaneously, effectively
implementing your own parallelism parameter within the script.

This is frustrating because the nsrclone command seems to
support separate pathnames without lumping everything under one common
path.

I don't think this is a fair comparison. nsrclone is working with SSIDs
that already exist, so it is easier to work with multiple save sets.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=