KDirWatcher and dnotify signal problem

Lubos Lunak l.lunak at sh.cvut.cz
Mon Sep 2 17:01:16 BST 2002


 could somebody please review the attached patch? The theory is about like 
this: Whoever implemented the dnotify support in KDirWatch simply copied the 
example from kernel documentation. And the example uses SIGRTMIN for the 
signal. And LinuxThreads seem to use SIGRTMIN for its internal purposes in 
some configurations. So since the switch to Qt3 dnotify probably didn't work 
that great.

 I've found some internal function in glibc for allocating the real-time 
signals and modified KDirWatch to use it. Could somebody review it?

 BTW, now that the dnotify support finally seems to work, could it be enabled 
by default?

Lubos Lunak
KDE developer
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configure.in.in.patch
Type: text/x-diff
Size: 530 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20020902/7c8068ea/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdirwatch.cpp.patch
Type: text/x-diff
Size: 1650 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20020902/7c8068ea/attachment-0001.patch>

More information about the kde-core-devel mailing list