[mythtv-users] mythlogserver fixes/0.26 OS-X?

[Craig Treleaven]

At 12:58 PM +1100 2/17/13, Jean-Yves Avenard wrote:
>On 17 February 2013 07:49, Craig Treleaven <ctreleaven at cogeco.ca> wrote:
>>  OK, I've been doing some more testing.  I've found that, on OS X, I can't
>>  let Myth launch mythlogserver.  If launched with the --daemon flag, OS X
>>  refuses to run it.  If I patch out the --daemon flag, it launches OK but the
>>  program that caused it to launch (eg mythfrontend or mythtv-setup) will
>>  appear to hang when you try to exit.  If you wait for the 5 minute timer to
>>  elapse, mythlogserver will quit and _then_ your program will finish.  Pretty
>>  undesirable behaviour.
>
>I posted a patch that gets around the issue completely.
>There's really no need to start mythlogserver in daemon mode. The way
>it is started is from a process that has already forked. So there's no
>point forking again just so it run in the background: it is already
>running in the background

Doesn't that still leave the issue that, on exit, the parent seems to 
hang until the child exits (ie 5 minutes, at best)?  Eg, launch 
mythtv-setup, which launches mythlogserver (no --daemon flag), do 
whatever, exit mythtv-setup.  For me, mythtv-setup waits until 
mythlogserver times out (or I kill it) before returning control to 
the terminal.  I believe if I were to launch another Myth program, 
the shutdown timer on mythlogserver would be cancelled and the 
original parent process would continue to be frozen.

On OS X, is the easiest workaround to make the shutdown timer 
effectively zero?  (Looks to me like there are two places that need 
to be patched in libmythbase/loggingserver.cpp.)

All the testing I've done has been with mythtv-setup as I don't have 
a complete 0.26 test system, yet.

Craig