[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Bug#38142: wrong wallpaper list kills xlock (fwd)
From:       David Faure <david () mandrakesoft ! com>
Date:       2002-02-27 23:07:31
[Download RAW message or body]

On Tuesday 26 February 2002 10:36, Josef Weidendorfer wrote:
> Hi,
> 
> I don't know anything about the SaverEngine, but a good way to start
> a daemon is to fork 2 times, and let the first fork exit. This way, the daemon 
> gets init (PID 1) as parent, and has no connection to the orig process.

Thanks for the hint... but I don't see how to combine this with KProcess :(
lockeng.cc uses a KProcess for the screensaver process, to be able to
know when it exited (although... SaverEngine::hackExited() doesn't make much
sense to me). .. and also to be able to terminate the screensaver by force (stopSaver(),
calls stopHack()). Not sure how to do all of this with 2 forks. Waldo, you're
the expert about such stuff, aren't you ?  /me trying flattery ;)

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://people.mandrakesoft.com/~david/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today


[prev in list] [next in list] [prev in thread] [next in thread]