udev signal handler should not syslog()
Please remove any syslog() from the signal handler! According to
http://www.opengroup.org/onlinepubs/000095399/functions/xsh_chap02_04.html
this is unsafe and we see hangups in vmware where SIGALRM is fired up.
Quoted 4 lines · Harald Hoyer
Please remove any
syslog()from the signal handler! According to
http://www.opengroup.org/onlinepubs/000095399/functions/xsh_chap02_04.html
this is unsafe and we see hangups in vmware where SIGALRM is fired up.
the tdb_close() used in the signal handler, contains free() calls, which seem to be dangerous as well!
Quoted 4 lines · Harald Hoyer
Please remove any
syslog()from the signal handler! According to
http://www.opengroup.org/onlinepubs/000095399/functions/xsh_chap02_04.html
this is unsafe and we see hangups in vmware where SIGALRM is fired up.
Right, this should be fixed. I'll wait for a decision regarding the tdb code. If the multi-file-db will work well for the thousands of disks setup, all this stuff will go anyway.
udev_log="no" in /etc/udev/udev.conf should fix that in the meantime for users running into trouble with that.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id065&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel