tags 426049 upstream patch
stop
Michael Biebl <[EMAIL PROTECTED]> writes:
> Zitat von Antoine Cellerier <[EMAIL PROTECTED]>:
>
>> On Sat, May 26, 2007, Michael Biebl wrote:
>>> Could you please attach the output of "hald --daemon=no --verbose=yes"
>>> to this bug report (After stopping the running hald instance).
>
>> *** [DIE] osspec.c:watch_fdi_files():349 : Unable to initialize
>> inotify: Function not implemented
>
> You have compiled your own kernel and missed to enable inotify support.
> (Re)compile your kernel with inotify support or use the Debian kernel,
> which has inotify support.
Yes, looking at the source, the new upstream version seems to require a
kernel with inotify support now. This is an upstream issue of course,
and it would be kind if you could ask upstream to not require inotify.
Nevertheless, this should be at least documented. Better would be a
check in the preinst or initscript which gives a warning like the
following patch:
=== modified file 'debian/hal.init'
--- debian/hal.init 2007-06-04 12:51:47 +0000
+++ debian/hal.init 2007-06-04 12:55:30 +0000
@@ -47,6 +47,11 @@
case "$1" in
start)
+ if [ ! -d /proc/sys/fs/inotify ]; then
+ log_failure_msg "Not starting $DESC - enable inotify support in
your kernel"
+ exit 0
+ fi
+
log_daemon_msg "Starting $DESC" "$NAME"
do_start
log_end_msg $?
This would smoothen the upgrade path and avoid a dpkg breakage if
running on a system without inotify.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
