From: Jim McCloskey <mcclosk@ucsc.edu>
To: linux-hotplug@vger.kernel.org
Subject: udev boot delay
Date: Fri, 04 Mar 2005 08:47:32 +0000 [thread overview]
Message-ID: <20050304084732.GA4203@branci40> (raw)
I'm not sure if this is a udev issue or a Debian issue.
After a recent upgrade to Debian testing on my laptop, which brought
udev to version 0.053, I experienced the following problem.
At the point in the boot-process where the init scripts run, I get this
message:
----------------------------------------------------------------------
It has been detected that the command:
/etc/rcS.d/S04udev
has been run from an interactive shell. It will probably not do
what you expect, so this script will wait 60 seconds before
continuing. Press ^C to stop it.
RUNNING THIS COMMAND IS HIGHLY DISCOURAGED!
----------------------------------------------------------------------
The init process does indeed pause for 60 seconds, but everything is
fine at the end.
I found this very puzzling, since I don't believe that udev has ever
been run from an interactive shell on this machine. I looked in
/etc/init.d/udev and found that the source of the warning was this:
----------------------------------------------------------------------
warn_if_interactive() {
TTY=$(my_tty)
if [ -z "$TTY" -o "$TTY" = "/dev/console" ]; then
return
fi
----------------------------------------------------------------------
And that explained to me why the problem arose only on the laptop and
not on the desktop machines that I manage. On the laptop (but not on
the others), I have in /etc/lilo.conf:
append="console=/dev/tty6"
And indeed when I commented out this line, the normal boot-behaviour
was restored, the warning was not issued, and there was no 60 second
pause.
But surely this isn't reasonable behaviour? In this circumstance, the
script is being run in a routine way and there is no real sense in
which it has been run from an interactive shell.
Jim
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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
next reply other threads:[~2005-03-04 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 8:47 Jim McCloskey [this message]
2005-03-04 9:12 ` udev boot delay Marco d'Itri
2005-03-04 14:00 ` Samuel Liddicott
2005-03-04 15:02 ` Olaf Conradi
2005-03-04 16:14 ` Marco d'Itri
2005-03-05 22:15 ` Olaf Conradi
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=20050304084732.GA4203@branci40 \
--to=mcclosk@ucsc.edu \
--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).