KDirWatcher and dnotify signal problem
bastian at kde.org
Thu Sep 5 19:38:02 BST 2002
-----BEGIN PGP SIGNED MESSAGE-----
On Thursday 05 September 2002 06:33 am, Lubos Lunak wrote:
> However, we should probably do something with the signal used. We're a
> library and when just hardcoding SIGRTMIN this may clash with other piece
> of code using SIGRTMIN. My original patch uses __libc_allocate_rtsig(),
> which is not documented, and doesn't help much if somebody else hardcodes
> SIGRTMIN anyway. I suggest we simply change SIGRTMIN to e.g. (SIGRTMIN+15).
That's fine with me.
We should also add a runtime check for a working dnotify somewhere don't you
think? If we make the use of DNOTIFY dependant on an env. variable then we
can check in kcminit whether DNOTIFY works in combination with the linux
kernel in use and set this env. variable accordingly.
I guess we should add the check to kded even instead of kcminit, since kded is
the first process to use kdirwatcher.
bastian at kde.org | SuSE Labs KDE Developer | bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
More information about the kde-core-devel