All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gabor Z. Papp" <gzp@papp.hu>
To: linux-hotplug@vger.kernel.org
Subject: Re: inotify_init failed
Date: Wed, 12 Nov 2008 14:24:10 +0000	[thread overview]
Message-ID: <x6od0lxbsl@gzp> (raw)
In-Reply-To: <x6wsfaxolc@gzp>

* "Kay Sievers" <kay.sievers@vrfy.org>:

| If you do:
|   killall udevd
|   strace /sbin/udevd
|   /sbin/udevd --daemon

| What does the strace print while udevd is the inotify calls? It looks
| like this here:
|   ...
|   inotify_init()                          = 3
|   inotify_add_watch(3, "/lib/udev/rules.d", ...) = 1
|   inotify_add_watch(3, "/etc/udev/rules.d", ...) = 2
|   inotify_add_watch(3, "/dev/.udev/rules.d", ...) = 3
|   ...

[...]
unlink("/dev/.udev/uevent_seqnum")      = -1 ENOENT (No such file or directory)
open("/dev/.udev/queue", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory)
open("/sys/kernel/uevent_seqnum", O_RDONLY|O_LARGEFILE) = 8
read(8, "1791\n", 31)                   = 5
close(8)                                = 0
stat64("/dev/.udev", {st_mode=S_IFDIR|0755, st_size\x100, ...}) = 0
open("/dev/.udev/uevent_seqnum", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0644) = 8
write(8, "1791\n", 5)                   = 5
close(8)                                = 0
fork()                                  = 2025
close(6)                                = 0
close(7)                                = 0
close(4)                                = 0
close(5)                                = 0
unlink("/dev/.udev/uevent_seqnum")      = 0
open("/dev/.udev/queue", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory)
[2025] main: inotify_init failed: No such file or directory
exit_group(0)                           = ?
...

  parent reply	other threads:[~2008-11-12 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 15:35 inotify_init failed Gabor Z. Papp
2008-11-11 15:45 ` Kay Sievers
2008-11-12 14:24 ` Gabor Z. Papp [this message]
2008-11-13  0:46 ` Kay Sievers
2008-11-13 14:03 ` Gabor Z. Papp
2008-11-13 14:17 ` Kay Sievers
2008-11-13 14:20 ` Gabor Z. Papp
2008-11-13 14:22 ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x6od0lxbsl@gzp \
    --to=gzp@papp.hu \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.