linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevsend: main: error sending message: Connection refused
Date: Fri, 25 Nov 2005 17:25:14 +0000	[thread overview]
Message-ID: <20051125172514.GB30663@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0511251449580.6610@dyndns.pervalidus.net>

On Fri, Nov 25, 2005 at 03:12:46PM -0200, Frédéric L. W. Meunier wrote:
> On Fri, 25 Nov 2005, Kay Sievers wrote:
> 
> >On Fri, Nov 25, 2005 at 02:55:11PM -0200, Frédéric L. W. Meunier wrote:
> >>I installed udev 076 and got a bunch of these. After it booted,
> >>no devices for modules were created. Then, I ran
> >>/sbin/udevstart and thew were crated.
> >>
> >>What may be wrong ? Could it be related to unix being a
> >>module and not built-in ? Using 2.6.14.
> >
> >Did you read the last section in the RELEASE-NOTES for 076? If not, read
> >the first section of the README too. :)
> 
> OK, I'll change CONFIG_UNIX next time.

Socket as a module does not make sense, but it should work, if you have
module auto-loading.

> But does the RELEASE-NOTES part mean the distributed start_udev 
> (what I use) needs to be upgraded ?

Good point, I will just delete that silly thing. Seems I've missed it
with the recent removal of all the misleading stuff that is no longer
correct.

> The only reference I see 
> for udevd is 'udevd=/sbin/udevd'.

No, your init script, which depends on the distro how it must look
like, needs to start udevd --daemon. This will no longer happen magically
through udevsend. See this in the the README file:
  http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=blob;hb=HEAD;f=README#l42

Kay


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&opÌk
_______________________________________________
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

      parent reply	other threads:[~2005-11-25 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-25 16:55 udevsend: main: error sending message: Connection refused Frédéric L. W. Meunier
2005-11-25 16:58 ` Marco d'Itri
2005-11-25 17:01 ` Kay Sievers
2005-11-25 17:12 ` Frédéric L. W. Meunier
2005-11-25 17:25 ` 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=20051125172514.GB30663@vrfy.org \
    --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).