Petri Helin wrote:
Udo Richter wrote:
In any case, try dumping the return value to syslog, I would really like
to know what additional flag is set on the return value.
I got 6, 9 and 11 when I did some debugging earlier.
I *think* that these are kill signals received by the child process.
Petri Helin wrote:
Udo Richter wrote:
I *think* that these are kill signals received by the child process.
Which is strange, as the child does an exit immediately. (Unless you're
somewhere between 1.5.1 and 1.5.3 - this changed in 1.5.4)
6 is SIGABRT, 11 is SIGSEGV and 9 is SIGKILL.
I
On 8/9/07, Udo Richter [EMAIL PROTECTED] wrote:
Petri Helin wrote:
Udo Richter wrote:
I *think* that these are kill signals received by the child process.
Which is strange, as the child does an exit immediately. (Unless you're
somewhere between 1.5.1 and 1.5.3 - this changed in 1.5.4)
Petri Helin wrote:
It seems to me that VDR still fails writing the NextWakeupTime every now
and then, even after I made the change described earlier. Do you have
suggestions on how to shutdown properly in order to get the
NextWakeupTime written to setup.conf? I run VDR as a daemon and shut
Udo Richter wrote:
In any case, try dumping the return value to syslog, I would really like
to know what additional flag is set on the return value.
I got 6, 9 and 11 when I did some debugging earlier.
-Petri
___
vdr mailing list
Udo Richter wrote:
Petri Helin wrote:
I traced the problem to the SystemExec call in
cShutdownHandler::CallShutdownCommand where Setup.NextWakeupTime is
updated only if the SystemExec call returns 0. i changed it to accept
all values greater or equal to 0 and now Setup.NextWakeupTime gets
