udevsend: main: error sending message: Connection refused
ken at linuxfromscratch.org
Wed Feb 1 05:16:17 PST 2006
Long ago, On Wed, 18 Jan 2006, Jim Gifford wrote:
> Back Michael (extern) wrote:
>> I build the clfs. After the final reboot I get the message
>> "udevsend: main: error sending message: Connection refused"
>> What failure could I have done by build the clfs system?
>> Thanks for help
> You can safely ignore this error. We are working to resolve it, upstream said
> it was common.
Actually, there _is_ a problem here - hotplugging in the current book
doesn't work (or maybe doesn't _all_ work), although it's mostly a BCLFS
issue (example - I've got a usb printer, the device node for
/dev/usb/lp0 isn't created).
I eventually found a post from Kay on the hotplug list, saying that
from udev076 the initscript has to start udevd --daemon (this apparently
used to happen through udevsend).
A patch follows which fixes the udev initscript in init.d on a built
system, works for me with 220.127.116.11. I'm open to suggestions/advice on
how to handle this for the book (probably, the problem will disappear
when the new udev stuff goes in ?) Do we need new bootscripts for the
short term, or would a patch be better (the problem is only in clfs, lfs
is still using an older udev) ?
--- udev.bak 2006-02-01 01:30:00.000000000 +0000
+++ udev 2006-02-01 01:43:42.000000000 +0000
@@ -69,6 +69,9 @@
# and save it's status so we can report failures.
udevstart || failed=1
+ # for udev076 onwards, run udev as a daemon, it is no longer automatic
+ /sbin/udevd --daemon
# Now, create some required files/directories/devices that sysfs
# doesn't export for us.
das eine Mal als Tragödie, das andere Mal als Farce
More information about the cross-lfs