Discussion:
inotify and udevd
Frédéric L. W. Meunier
2006-06-16 18:43:26 UTC
Permalink
Sometimes "main: the kernel does not support inotify, udevd
can't monitor configuration file changes" from udevd apear in
my logs, but I always had

CONFIG_INOTIFY=y
CONFIG_DNOTIFY=y

in my kernels. What triggers it ?
--
How to contact me - http://www.pervalidus.net/contact.html
Kay Sievers
2006-06-16 19:20:51 UTC
Permalink
Post by Frédéric L. W. Meunier
Sometimes "main: the kernel does not support inotify, udevd
can't monitor configuration file changes" from udevd apear in
my logs, but I always had
CONFIG_INOTIFY=y
CONFIG_DNOTIFY=y
Try to strace the udevd startup. It should look like:
$ strace -t /sbin/udevd
...
21:16:00 inotify_init() = 7
21:16:00 inotify_add_watch(7, "/etc/udev/rules.d", IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE) = 1
...

If you change a file in /etc/udev/rules.d/, it should wake up
on the inotify fd and reload the rules:
21:18:26 select(8, [3 4 5 7], NULL, NULL, NULL) = 1 (in [7])
...

Kay
Kay Sievers
2006-06-16 19:29:13 UTC
Permalink
Post by Kay Sievers
Post by Frédéric L. W. Meunier
Sometimes "main: the kernel does not support inotify, udevd
can't monitor configuration file changes" from udevd apear in
my logs, but I always had
CONFIG_INOTIFY=y
CONFIG_DNOTIFY=y
$ strace -t /sbin/udevd
...
21:16:00 inotify_init() = 7
21:16:00 inotify_add_watch(7, "/etc/udev/rules.d", IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE) = 1
...
If you change a file in /etc/udev/rules.d/, it should wake up
21:18:26 select(8, [3 4 5 7], NULL, NULL, NULL) = 1 (in [7])
...
And in the case you see the failure logged, what does:
ls -l /proc/$(pidof udevd)/fd
print?

(Also, please mention the distro, the kernel and udev version.)

Kay



_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-***@lists.sourceforge.net
https://lists.sourceforg

Loading...