Networker

Re: [Networker] Need help on nsradmin !!

2006-05-26 13:38:59
Subject: Re: [Networker] Need help on nsradmin !!
From: Jim Ruskowsky <jimr AT JEFFERIES DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 26 May 2006 13:33:46 -0400
I had a situation once where I could not use nsradmin to gather the 
information I needed - so I had this
skeleton of a script lying around.  Why not share it - as, most 
importantly, it provides a bit of insight
as to how networker stores its configuration.

I somehow had gotton into the situation where I had two default groups, 
and both the GUI and nsradmin
refused to delete them because the it is the "default" group.  I started 
poking around while waiting for
tech support to get back to me and found my two resources (in 
/nsr/res/nsrdb) belonging to the
group default.  I shut down networker, renamed one of the groups, 
restarted networker, then deleted
the renamed group.  I believe I probably could have simply deleted the 
resource file - but I though it
better to make as small a change as possible in case I missed something 
else.

One of the joys of unix is that there are numerous ways of accomplishing 
the same thing.  After all, what
do you think nsradmin is doing behind the scenes to query this 
information.

Darren Dunham <ddunham AT TAOS DOT COM> wrote on 05/26/2006 01:19:35 PM:

> > Here is a quick shell script to get you started (hope you are on a 
unix 
> > platform), which looks through the contents of the nsrdb resource 
files. 
> > It finds all the NSR client resources, and prints out the name of the 
> > client and the name(s) of the storage nodes.  Modify as needed.
> > 
> > for f in `find /nsr/res/nsrdb -type f`
> > do
> >         grep -l "type: NSR client;" $f > /dev/null &&  egrep "^storage 

> > nodes:|^name:" $f
> > done 
> 
> Why would you grab the files directly instead of just asking nsradmin?
> 
> show name; storage nodes
> print type:NSR client
> 





Jefferies archives and reviews outgoing and incoming e-mail.  It may be 
produced at the request of regulators or in connection with civil litigation. 
Jefferies accepts no liability for any errors or omissions arising as a result 
of  transmission. Use by other than intended recipients is prohibited.

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