From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#281107: udev: segfault while doing force-reload or restart
Date: Sat, 20 Nov 2004 23:47:48 +0000 [thread overview]
Message-ID: <1100994468.5030.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20041120191951.GA20077@wonderland.linux.it>
On Sat, 2004-11-20 at 20:19 +0100, Marco d'Itri wrote:
> ----- Forwarded message from "Jean-Luc Coulon (f5ibh)" <jean-luc.coulon@wanadoo.fr> -----
>
> Subject: Bug#281107: udev: segfault while doing force-reload or restart
> Nov 13 18:14:00 tangerine udev[5508]: creating device node '/dev/ttyab'
> Nov 13 18:14:00 tangerine udev[5508]: error: timeout reached, event probably not
> handled correctly
Maybe 30 seconds timeout are too short for the dev.d/ scripts or a slow
syslog. Later udev versions have 120 seconds and do not log in the
udevstart case.
> > > "Try running udevstart from the command line."
> > >
> > > I replied:
> > >
> > > "udevstart get frozen after a while, the latest devices created was:
> > > [ ... ]"
This is probably cause by using syslog() in a signal handler. It's fixed
in a later version.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-11-20 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 19:19 Bug#281107: udev: segfault while doing force-reload or restart Marco d'Itri
2004-11-20 23:47 ` Kay Sievers [this message]
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=1100994468.5030.36.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).