pid not cleared on error

[GoogleCodeExporter]

What steps will reproduce the problem?
1. process doesn't clear pid file from previous run
2. daemon.info still exists and contains a pid
3. another process gets the same pid number that is in daemon.info
Message is displayed:
CRITICAL 2062 RSSDler is already running. exiting.

What is the expected output? What do you see instead?
Maybe it should delete the daemon.info file when this error occurs.  At least, 
it would run the next time.

What version of the product are you using? On what operating system?
0.4.2

Please provide any additional information below.
Maybe another way to determine the running pid other than from a file or else 
some way to ensure the pid information is cleared on this error is needed.

If the existing pid is to some long running process then rssdler will continue 
to fail indefinitely until the daemon.info file is removed or cleared.  This 
can cause problems if running with cron because it can go unnoticed for some 
time.

Original issue reported on code.google.com by mark.fa...@gmail.com on 25 Aug 2010 at 10:52

[GoogleCodeExporter]

How do you exit? I believe `rssdler -k' clears pidfile properly. It's when you 
issue kill(1) that by default sends SIGTERM then rssdler doesn't clear pidfile.

Original comment by swell.k@gmail.com on 9 Oct 2010 at 11:02

Attachments:

• sigterm_is_exit.diff

[GoogleCodeExporter]

In my crontab I have: 
*/15 * * * * /usr/local/bin/rssdler -ro >/dev/null 2>&1

I also occasionally just run it manually to check if it is running correctly 
through cron.

$> rssdler -ro 
Threads have already been scanned.

Thanks

Original comment by mark.fa...@gmail.com on 9 Oct 2010 at 3:36

[GoogleCodeExporter]

Doh, I've overlooked that runOnce returns from main loop.

Original comment by swell.k@gmail.com on 9 Oct 2010 at 4:08

Attachments:

• clear_pidfile_after_runOnce.diff