Re: The udev question & understanding what runsvdir "means"

From: Alex Efros <>
Date: Wed, 1 Oct 2014 05:54:28 +0300


On Tue, Sep 30, 2014 at 11:28:08AM -0700, Avery Payne wrote:
> First, socklog-*, syslog, acpid, smartd, are all "outward" services in my
> definition, because something or someone, somewhere, can call upon them
> (send input), or consume their service (receive output). udevd is special,
> true, but to my knowledge, only the kernel really toys with it (or at least
> in theory). It wasn't *meant* to send input or output elsewhere, even
> though it *can*.

Hm. socklog-klog, mcelog works exactly how you explain - they take input
only from kernel and do their work without interacting with other
services, and no other users or services interact with them. Probably we
can also put acpid and smartd under same description. So, what's the real
difference between them and udev?

> Runit really, really needs a pause(1) command to assist with this.

Is `kill -STOP $$` at end of ./run won't be enough? Why do you need pause(1)?

> non-issue. How is this done currently with init.d scripts? I know Debian
> is doing something to pause execution while udev populates /dev...

I think this pause is done by `udevadm settle --timeout=30` command.

			WBR, Alex.
Received on Wed Oct 01 2014 - 02:54:28 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:18 UTC