Hi,
I have just made a couple small improvements to the freevo script. When it checks the running process list for that pid it also matched on the application name in case some other process is running as an old Freevo process id. Also we now remove the pid file when we think we're done with it.
-Rob
K. Creason wrote:
My record_daemon.py was constantly breaking due to the pid file in /var/run. The previous process isn't running - but that @[EMAIL PROTECTED] pid file was still there and stopping the next one. Actually, now that I think back, it's always still there but sometimes it would run and sometimes it wouldn't. And once it wouldn't, you couldn't get it to start again until you removed the pid file. What is with that? Shouldn't it be removed when the daemon exits?
I had to modify my cron entry: * * * * * cd /usr/local/freevo; ./freevo execute src/tv/record_daemon.py
/tmp/freevo.cron.out 2>&1 ; sleep 10; rm
/var/run/freevo-record_daemon.py.pid >>/tmp/freevo.cron.out 2>&1
Now I'm happy, but is it an accident waiting to happen?
-K
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
