On Tue, 2004-02-03 at 23:28, Martin Schlemmer wrote: > On Tue, 2004-02-03 at 22:13, Greg KH wrote: > > Except if I miss something major, udevsend and udevd still do not > work: > Skip that, it does work if SEQNUM is set :P Anyhow, is it _really_ needed for SEQNUM to be set? What about the attached patch? Then, order I have not really checked yet, but there are two things that bother me: 1) latency is even higher than before (btw Greg, is there going to be more sysfs/whatever fixes to get udev even faster, or is this the limit?) 2) events gets missing. If you for example use udevsend in the initscript that populate /dev (/udev), the amount of nodes/links created is off with about 10-50 (once about 250) entries. Thanks, -- Martin Schlemmer
--- udev-016/udevsend.c 2004-02-04 00:55:23.522428312 +0200
+++ udev-016.seqnum/udevsend.c 2004-02-04 00:57:37.898000120 +0200
@@ -149,10 +149,14 @@
seqnum = get_seqnum();
if (seqnum == NULL) {
+#if 0
dbg("no seqnum");
goto exit;
+#endif
+ seq = 1;
+ } else {
+ seq = atoi(seqnum);
}
- seq = atoi(seqnum);
sock = socket(AF_LOCAL, SOCK_STREAM, 0);
if (sock == -1) {
Attachment:
signature.asc
Description: This is a digitally signed message part
Follow-Ups: References:
- [ANNOUNCE] udev 016 releaseGreg KH
- Re: [ANNOUNCE] udev 016 releaseMartin Schlemmer
- Prev by Date: Re: 2.6.0, cdrom still showing directories after being erased
- Next by Date: Re: [PATCH] 2.6.1 Hyperthread smart "nice" 2
- Previous by thread: Re: [ANNOUNCE] udev 016 release
- Next by thread: Re: [ANNOUNCE] udev 016 release
- Indexes:[Main][Thread]