Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Networker\]\s+using\s+backup\s+command\s+on\s+clients\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Networker\]\s+using\s+backup\s+command\s+on\s+clients\s*$/: 2 ]

Total 2 documents matching your query.

1. [Networker] using backup command on clients (score: 1): Author: Bill Hewitt <bill AT INF.ED.AC DOT UK>; Date: Thu, 26 Oct 2006 16:44:41 +0100; Fron the nwadmin gui, if you use 'backup command' on a client, rather than the generic save, is there a safe way to process the arguments that save would have got. An example script is for backing up; /usr/local/webapp/mharc-adsm.org/html/Networker/2006-10/msg00300.html (12,027 bytes)
2. Re: [Networker] using backup command on clients (score: 1): Author: Darren Dunham <ddunham AT TAOS DOT COM>; Date: Thu, 26 Oct 2006 12:50:19 -0700; Yes. Create a wrapper script and use that script to call 'save' after processing the arguments. Right. I'm not sure what you mean by "doesn't seem to work very well". What *does* it do? Does /tmp/aa; /usr/local/webapp/mharc-adsm.org/html/Networker/2006-10/msg00305.html (13,479 bytes)

Current List: 1 - 2
Page: [1]