Menu

#785 Sending USR2 signal to logd is not resulting in the expected behaviour

never
invalid
nobody
None
defect
log
-
4.2
minor
2015-07-14
2014-02-14
manu
No

Execution of the following command on the controller node does not lead to any trace file as mentioned in the logsv README
pkill -USR2 osaflogd

However kill -12 pgrep osaflogd worked. The README needs to be updated accordingly.

Related

Tickets: #142

Discussion

  • elunlen

    elunlen - 2015-04-14

    This is no longer an issue. Command does work in current OpenSAF UML cluster

     
  • elunlen

    elunlen - 2015-04-14
    • status: unassigned --> invalid
     
  • Sirisha Alla

    Sirisha Alla - 2015-04-15

    I think this ticket requires a documentation update. pkill -USR2 osaflogd in the README needs to be corrected since it does not work.

     
  • elunlen

    elunlen - 2015-04-15

    I have tested pkill -USR2 osaflogd on OpenSAF started in the UML environment and it works so the README is correct.
    However pkill may not work in all shells/versions so the READMe could be updated with some more generic info saying that tracing can be started by sending SIGUSR2 (12) signal to the osaflogd process on the SC node where tracing shall be started and pkill -USR2 osaflogd and kill -12 pgrep osaflogd could be given as examples of how to do that.

     
  • Nagendra Kumar

    Nagendra Kumar - 2015-07-14
    • Milestone: future --> never
     

Log in to post a comment.