Sorry to resend this but I got zero responses...

I've noticed in the archives and in the faqs that the steps to renaming
always includes shutting down NetWorker.  I don't have the luxury of
shutting down very often, so I've always renamed without shutting down.
To this point I've never had a problem, but I just wanted to make sure
I'm not setting myself up for trouble later.  What is the reasoning
behind the shutdown?

Also I've written a script(still unpolished) that does the whole
renaming process for you if anyone is interested... Obviously it may
need to be edited to meet your sites requirements, but is something to
work with.

Thanks!

Joel

Hey All,
 
Why does everyone recommend shutting down NetWorker to rename a client?
I've renamed several clients without shutdowns without any apparent
effect.  Am I just not seeing a potential gotcha or is it just a good
thing to try to do?  In my environment I can't shutdown the server
nearly as often as I need to rename clients.
 
Side note... why in the heck doesn't Legato just allow you to rename
within the GUI.  It seems like it would be such and easy and appreciated
feature to add.  Maybe they have in the newer versions...
 
Thanks,
 
Joel

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=