#2 Exit 0 on error

closed-fixed
nobody
None
5
2009-01-23
2008-09-12
Anonymous
No

When devmon cannot write to the pid file on startup (in my case because the directory did not exist) it exits quietly. No log entries. Exit code 0.
Required to run with -f -vvvvvvv to see error on stdout.

Discussion

  • Buchan Milne

    Buchan Milne - 2008-12-08

    Unfortunately by the time the pid file is written, the original process has returned, the pid file is written by the forked copy (except when run in the foreground, when forking does not occur).

    However, logging regarding failures to write to the pid file were not making it to the log file (because it was opened too late). I have fixed this, so the log file should contain a suitable error message.

    However, this leaves the fact that inability to open the log file will not be logged anywhere. I will try and find a solution to that later.

    I'm marking this as fixed as the log file should report the inability to write to the pid file.

     
  • Buchan Milne

    Buchan Milne - 2008-12-08
    • status: open --> open-fixed
     
  • Buchan Milne

    Buchan Milne - 2008-12-08

    For the same reason, it might not help to return a non-zero exit code, but I have added return codes of 1 for any failure, but it won't be propagated in all cases.

     
  • Buchan Milne

    Buchan Milne - 2009-01-23

    Should be fixed in 0.3.1-beta1. Closing since this item was logged anonymously.

     
  • Buchan Milne

    Buchan Milne - 2009-01-23
    • status: open-fixed --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks