I am trying to troubleshoot an interoperability problem between Networker 6.1.1 and my company's product, and I need some advice on how to maximize the verbosity of the loggining information produced by networker. Unfortunately I cannot find any documentation on this. The environment is windows 2000, SP2. Are there ways to maximize the verbosity/debug info? Especially, can it be done from within the GUI, or would it be necessary to run backups via the command line? Or better yet, is there a resource file that Legato consults? I am interested in both client and server side diags, as it is a networking problem I am working on.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Need help on gathering diagnostic information.
- Thread starter babel17
- Start date
if you require more information, i.e. debugging etc, then you need to run the nsrd process using the parameter -D
i.e.
shutdown networker
restart networker as follows
# nsrexecd
# nsrd -D3
the -D option has levels 1-9 but when you get past 4 the information is too verbose and only good for Legato spec's to anaylse, we usually use level 3, then when you check out the daemon.log etc the ammount of feedback is a lot better.
p.s. dont use these for normal use as the log files will grow to extreme sizes
i.e.
shutdown networker
restart networker as follows
# nsrexecd
# nsrd -D3
the -D option has levels 1-9 but when you get past 4 the information is too verbose and only good for Legato spec's to anaylse, we usually use level 3, then when you check out the daemon.log etc the ammount of feedback is a lot better.
p.s. dont use these for normal use as the log files will grow to extreme sizes
- Status
Similar threads
- Locked
- Question