From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Tue, 17 Jan 2006 20:43:03 +0000 Subject: Re: Cold plug starting services too soon Message-Id: <20060117204303.GA28886@vrfy.org> List-Id: References: <20060117203244.GA3135@kroah.com> In-Reply-To: <20060117203244.GA3135@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, Jan 17, 2006 at 12:32:44PM -0800, Greg KH wrote: > > > Hi Kay and Marco. > > Gentoo has run into the problem that if we load modules for some types > of devices (like network devices for example), we can generate hotplug > events that want to run things on disks that are not mounted yet, as we > havn't even done mounting of the non-root filesystem yet (caused by udev > doing the coldplug pretty much the first thing at boot time.) > > How has Debian and SuSE kept from having this issue? I think for SuSE > we rely on the fact that the initrd/initramfs has loaded the proper > modules already for us, right? All running events are exported in /dev/.udev/queue/, events that fail will be moved to /dev/.udev/failed/. Make sure the script return non-zero if it can't run and retry all failed events from /dev/.udev/failed/ after "localfs" is done. If the same event then runs successfully, it will go away from /dev/.udev/failed/. On SUSE I have a second udev boot script that is called /etc/init.d/boot.udev_retry. 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://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ 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