[PATCH] KDirWatch, DNOTIFY, SIGIO/SIGPOLL, BR50014

[Waldo Bastian]

Hello,

BR50014 complaints about kded dieing on a SIGPOLL signal. It's a bit a mystery 
why we get a SIGPOLL but it appears that we can get a SIGPOLL as part of the 
DNOTIFY signalling, when the kernel queue for DNOTIFY signals overflows, it 
sends a SIGPOLL to indicate that situation.

See e.g. http://groups.google.com/groups?oi=djq&selm=an_366163395
(SIGIO and SIGPOLL are the same signal)

The following patch adds support for this feature to kdirwatch. 

BR50014 remains a mystery because under normal situations kded will be fast 
enough to handle incoming DNOTIFY signals. 

To test / reproduce, stop kded and run it from a terminal with:
	kded --nofork

Then run the following script:
	export a=$HOME/.kde/share/applnk/bla
	while touch $a; do rm $a;done

On my PC this does not cause problems for kded, but if you suspend (^Z) kded 
and then resume it again (fg) kded will receive a SIGPOLL.

Cheers,
Waldo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdirwatch_sigio.diff
Type: text/x-diff
Size: 2525 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20021119/1395ad23/attachment.diff>