[Lcdproc] Running Problems

[brian]

Peter Marschall wrote:
> Hi,
> 
> On Tuesday, 22. May 2007 23:28, brian wrote:
>> [...] You also won't be able to
>> set LCDd to start automatically during the boot process, since it'll hang
>> there waiting for the signal back from the child process (and, in my
>> situation, you cannot do anything about it yet, as the sshd daemon hasn't
>> yet started, so I can't get to the system to "push it along")
> 
> Then, why don't you change the order in which sshd and LCDd are started
> at boot time?

   umm... because that wouldn't be a proper (or complete) fix?  That's only marginally less inane than writing a separate daemon 
that does nothing other than kill of the LCDd parent after the child has successfully spawned.

I've disabled LCDd from starting automatically on my machine, as that (if I were to start sshd earlier in the boot process, or LCDd 
were started later) would *still* require that I stand by to "manually assist" it's daemonization process, every time the machine is 
booted (or rebooted).   In it's current [broken] state, LCDd doesn't just not load itself correctly, it halts the entire boot 
process until manually 'pushed'.

It would be far more efficient to simply address the LCDd problem within the LCDd source, wouldn't it?