NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
I was using short hand... look up the process ID and hit it with a USR2. [root@feed01 ~]$ ps ax | grep pqa 2583 pts/0 S+ 0:00 grep pqa 22124 ? S 195:19 pqact [root@feed01 ~]# kill -USR2 22124 It will cycle through levels of debug output in the syslog. -Tyler On Fri, Dec 10, 2010 at 12:28 PM, Jeff Lake - Admin <admin@xxxxxxxxxxxxxxxxxxxx> wrote: > daryl, Tyler .. > huh ?? > "kill -USR2 pqact" > I must be having a Linux dunce moment .. > > -bash: kill: pqact: arguments must be process or job IDs > > so I guess I need to find process ID assigned to the logger > or LDM itself ?? > > -Jeff > > _______________________________________________ > ldm-users mailing list > ldm-users@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/
ldm-users archives: