From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier Blin Date: Mon, 03 Oct 2005 17:44:39 +0000 Subject: Re: [RFC] coldplug - emit hotplug events from sysfs Message-Id: List-Id: References: <20051001124943.GA26076@vrfy.org> In-Reply-To: <20051001124943.GA26076@vrfy.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Scott James Remnant writes: > On Mon, 2005-10-03 at 17:29 +0200, Kay Sievers wrote: > >> I don't see how to use a udev rules to continue the init script which >> depends on the tty's to be around after that. Care to explain? >> > e.g. for each of /sys/class/t*/*, write the name into a file > (/tmp/waiting) and write to the uevent... in a udev rule for events, > remove the line from the /tmp/waiting file. > > Sleep until the /tmp/waiting file is zero bytes in size. > > > Ok, that's just as hacky as grovelling around in ps I guess, but at > least it has the advantage that there's no possibility of no udev > processes having been started by the next line of shell - which there is > with your example. > > There's almost certainly a more elegant way, but basically mark the > events you're waiting for and wait for them all to come back. We could have a lock directory, in which a lock file would be added for each event (using the full path with '/' replaced by '%' for example). This lock file would be removed once udev is done processing the event. But is it easy to remove a lock file when a PROGRAM or RUN rule is used? Maybe by catching signals of this program. -- Olivier Blin Mandriva ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ 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