> What I wanted is multiple save sets, so each path or directory has its 
> own unique name. Obviously, one save command will create a single ssid, 
> so I will need to write something to launch multiple saves, one for each 
> path, but not to exceed the desired parallelism for the client.

Can I ask why?  I'm sure there's some reasons, but this seems rather
esoteric.  I'd like to make sure were not overlooking some other way of
handling this.

> I have indexing turned off on the pool, so no need to worry about the 
> client index becoming too large, and these are run on an adhoc basis.

I doubt it'll be too large if you're not doing them often, but indexing
on the pool only affects whether the indexes will be sent to tape, not
whether they are stored.  You'd need to turn the browse period down to
reduce the impact of index storage on the disk.

-- 
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