Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Networker\]\s+default\s+client\-\-how\s+to\s+check\s+via\s+nsradmin\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Networker\]\s+default\s+client\-\-how\s+to\s+check\s+via\s+nsradmin\?\s*$/: 2 ]

Total 2 documents matching your query.

1. [Networker] default client--how to check via nsradmin? (score: 1): Author: David Gold-news <dave2 AT CAMBRIDGECOMPUTER DOT COM>; Date: Wed, 16 Mar 2005 16:57:03 -0500; Hi, I'm seeing a case with Networker 7.1.3 where I have two client objects for the networker server (one for daily, one for monthly backups--we separate into pools based on groups), and even though I; /usr/local/webapp/mharc-adsm.org/html/Networker/2005-03/msg00172.html (12,266 bytes)
2. Re: [Networker] default client--how to check via nsradmin? (score: 1): Author: Dave Mussulman <mussulma AT CS.UIUC DOT EDU>; Date: Wed, 16 Mar 2005 17:30:14 -0600; There's not a concept of a 'default client' in Networker. What you're seeing that indexes are associated with the server, not with the client, so indexes get the retention period for the server. If t; /usr/local/webapp/mharc-adsm.org/html/Networker/2005-03/msg00173.html (12,536 bytes)

Current List: 1 - 2
Page: [1]