From: Robert Rozman <rozman@fr...> - 2006-02-26 10:54:00
on few recent days I notice that motion tends to come into <defunct> state.
if I kill it and start it again it starts cleanly ....
Since motion runs under other application I have no access to its logs. does
it ouput anything to system logs ? Which ones ?
Thanks in advance,
Robert Rozman, 26.02.2006 11:53:
> on few recent days I notice that motion tends to come into <defunct>
> state. if I kill it and start it again it starts cleanly ....
> Since motion runs under other application I have no access to its logs.
> does it ouput anything to system logs ? Which ones ?
As always, the excellent Motion Guide should have been your starting
point. First guess of mine was to look here:
You'll find there a paragraph about error logging near the bottom -
syslog support is there, ok. (I knew before, but just to prove it ...)
The default file is '/var/log/syslog'. If you or your distribution is
setting up syslog in a custom way, the messages certainly can go
elsewhere. Your description doesn't give details of your system, so
not much to help you with this. At least take a look into
Another common move is to start Motion from the console and not let it
go to daemon mode. Carefully studing the page mentioned above there is
a special "verbose" command line option
So you should get a lot of messages, enough? :-)