>
> Is there a command or other slick method to get a list of the groups a
> client belongs to other than using nsradmin like:
>
> nsadmin> . type: NSR client; name: clientname
> nsradmin> print

Can I ask why you don't like that method?  What are you looking for in
an alternative that the above method doesn't do?

> I'm trying to build a list of expected savesets for each client, and
> some of my clients have multiple NSR client resources, each belonging to
> a different group.

Hmm.  Okay.  Maybe you don't really want all the groups, but you want
all the savesets?

Unfortunately, if any of the instances use 'all', then you'll have to
ask the client exactly which savesets it would send.  That complicates
things.  Otherwise...

nsradmin> show save set
nsradmin> print type:nsr client; name: myclient

> I've noticed that using something like 'savegrp -p -c
> client group' does work, but would need to be run for each group the
> client belongs to in order to get a list of all the expected savesets.

Yes.  But you could get all the groups from the nsradmin above.  Also,
you may not want every group, but every active group?

> How can I determine the group other than nsradmin or simply having a
> hard coded text file containing this information?

Again, I wonder what form you want the possible groups to be in.



--
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=