rader AT GINSENG.HEP.WISC DOT EDU wrote:

> > I find it hard to believe that cloning preserves multiplexing, it's my
> > understanding that nsrclone goes one by one, SSID to the next SSID
> > cloning each singly before moving on to the next

> It doesn't need to do that (at least not in the situations I've used
> it), and it's very easy to test.

> > Instead of copying one ssid at a time, it can maintain a list of ssids.

> As it streams a source volume, data from any matching ssid is copied to
> a destination volume.  This has the big benefit of requiring only a
> single pass on a source volume.

And so for many years we've been semi-manually doing something like...

 BEGIN='05Jan07 2359'; END='06Jan07 2359'
 QUERY="'!incomplete,level=full,'savetime>$BEGIN,savetime<$END"
 mminfo -r ssid -q "$QUERY" > ssidlist
 nsrclose -S `cat ssidlist`

Is there a better way these days?

How about just nsrclose -b pool -S -f ssidlist

steve - - - systems & network manager

high energy physics
university of wisconsin

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

--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 4145       | Voice: (301) 713-3284 x210
1315 East West Highway        | Fax:   (301) 713-3301
Silver Spring, MD 20910-3282  | Web Site:  http://www.nodc.noaa.gov/

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