Alan,
An alternative to using nsr_render_log is to have the daemon.log file
written to in addition to the daemon.raw file, and then continue to do
the tail to view it.
# nsradmin –p nsrexecd
nsradmin> print type: nsr log; name: daemon.raw
nsradmin> update runtime rendered log: "/nsr/logs/daemon.log”
Update? yes
Restart nsrexecd after modifying the resource.
Rick
Alan Rubin wrote:
Hello,
We used to keep a tail going of our daemon.log, but we've just upgraded
from 7.3.3 to 7.4.4 and daemon.raw is certainly harder to follow. Is
there any way to get nsr_render_log to behave in a similar manner to
'tail -f' while providing the filtered/cleaned output from daemon.raw?
Regards,
Alan Rubin
Technician Unix
DCS Midrange Services
Phone: +61 (08) 8999 5111
Fax: +61 (08) 8999 7493
e-Mail: alan.rubin AT nt.gov DOT au
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 with 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
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 with 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
| 