Use of /dev/null on trace file with kill -usr2

Technote (troubleshooting)


This document applies only to the following language version(s):

English

Problem(Abstract)

Can trace debug level be increased with the kill -usr2 command if the file size was reset with /dev/null?

Environment

[root@nc9053115087 precision]# ls -lart ncp_disco.NCOMS.trace

-rw-------. 1 root root 285348248 May 6 15:16 ncp_disco.NCOMS.trace
[root@nc9053115087 precision]# cat /dev/null > ncp_disco.NCOMS.trace
[root@nc9053115087 precision]# ls -lart ncp_disco.NCOMS.trace
-rw-------. 1 root root 0 May 6 15:16 ncp_disco.NCOMS.trace
[root@nc9053115087 precision]# ps -ef | grep ncp_disco
root 30811 30485 0 May02 ? 00:55:20 ncp_disco -domain NCOMS -discoOnStartup 0 -latency 100000 -debug 0 -messagelevel warn -logdir /opt/IBM/tivoli/netcool/log/precision -tracefd 7
[root@nc9053115087 precision]# kill -usr2 30811
[root@nc9053115087 precision]# ls -lart ncp_disco.NCOMS.trace
-rw-------. 1 root root 63286 May 6 15:17 ncp_disco.NCOMS.trace
[root@nc9053115087 precision]#


Resolving the problem

The use of /dev/null as shown above can also be safely be followed with use of kill -usr2 to reduce the size of the trace file and then increase the debugging level.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Network Manager IP Edition

Software version:

3.9

Operating system(s):

Linux, Solaris

Reference #:

1636489

Modified date:

2014-06-27

Translate my page

Machine Translation

Content navigation