From: Chris Friesen <chris_friesen@sympatico.ca>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] convert udevsend/udevd to DGRAM and single-threaded
Date: Sat, 07 Feb 2004 07:06:25 +0000 [thread overview]
Message-ID: <40248E71.90102@sympatico.ca> (raw)
In-Reply-To: <40232F58.3040404@sympatico.ca>
Patrick Mansfield wrote:
> I mean, SOCK_DGRAM is an unreliable transport, so what happens if the
> transport drops packets? It might be unlikely, especially for the AF_LOCAL,
> but it is possible.
>
> I don't see any ack or retransmit code in udevsend.
Unix sockets are basically reliable. Barring something really wierd going on,
if the server is present, a blocking sendto() (with valid parameters, of course)
will succeed eventually, which guarantees that the message was queued up in the
server's receive buffer. If the server is not present, then you get an errno of
ECONNREFUSED, and you know to start the server.
From the man page: "Unix sockets are always reliable and don't reorder datagrams."
It would be easy to make it totally reliable by doing periodic retries in
udevsend and have udevd send back an ack when cleaning up the message after udev
completes. I could send this in if people are interested.
Chris
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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 prev parent reply other threads:[~2004-02-07 7:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 6:08 [PATCH] convert udevsend/udevd to DGRAM and single-threaded Chris Friesen
2004-02-06 11:27 ` Kay Sievers
2004-02-06 16:03 ` Robert Love
2004-02-06 16:58 ` Patrick Mansfield
2004-02-06 22:21 ` Greg KH
2004-02-06 22:22 ` Chris Friesen
2004-02-07 1:24 ` Patrick Mansfield
2004-02-07 2:04 ` Mike Waychison
2004-02-07 7:06 ` Chris Friesen [this message]
2004-02-07 7:32 ` Patrick Mansfield
2004-02-07 10:06 ` 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=40248E71.90102@sympatico.ca \
--to=chris_friesen@sympatico.ca \
--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).