Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*JR\-\s+Client\s+Option\s+set\s+vs\s+dsm\.opt\s+\(sys\)\s*$/: 3 ]

Total 3 documents matching your query.

1. JR- Client Option set vs dsm.opt (sys) (score: 1)
Author: JR Trimark <j.r.trimark AT AURORA DOT ORG>
Date: Tue, 8 Mar 2005 09:38:19 -0600
We are debating whether or not to use client option sets in addition to the dsm.opt file. A little history is needed for discussion sake: We are backing up data only, which is typically on another dr
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-03/msg00287.html (11,088 bytes)

2. Re: JR- Client Option set vs dsm.opt (sys) (score: 1)
Author: Daniel Sparrman <Daniel.Sparrman AT EXIST DOT SE>
Date: Tue, 8 Mar 2005 16:42:45 +0100
Using only thoose options would make the difference between using client optionsets and dsm.opt entries fairly small due to the fact all of thoose options are static ones. I always use client options
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-03/msg00288.html (12,362 bytes)

3. Re: JR- Client Option set vs dsm.opt (sys) (score: 1)
Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Tue, 8 Mar 2005 13:43:51 -0500
If it's easy for you to log in and set up the dsm.opt files for your servers, that's fine. In the case of someone whose clients are geographically scattered, and/or they don't have administration rig
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-03/msg00297.html (12,216 bytes)


This search system is powered by Namazu