Re: s6-rc:

# Precreate the control FIFO s6-mkfifo -m 0600 $S6_SCANDIR/.s6-svcan/control background { if { # Block until s6-svscan starts reading its control FIFO redir -w 8 $S6_SCANDIR/.s6-svcan/control # Do not leak the fd fdclose 8

Re: s6-rc:

Thank you. I used a simplfied version, since I have no logging concerns: # Precreate the control FIFO s6-mkfifo -m 0600 $S6_SCANDIR/.s6-svcan/control background { if { # Block until s6-svscan starts reading its control FIFO redir -w 8 $S6_SCANDIR/.s6-svcan/c

Re: s6-rc:

Maybe you can use 2 different directory scanned by s6-svscan(one s6-svscan command by directory). One for your boot process and the second for your X session. Then init your compiled database by s6-rc-init when your second directory is ready and bring up your service with s6-rc. Now you can make

Re: s6-rc:

Using the fifo trick [1]? As a side note, though the s6 documentation considers it "dirty", similar methods [2] are widely used for process synchronisation in CSP-style concurrency. [1] . [2]

s6-rc:

Hello, Trying to use s6-rc, I have run into something that looks like a race condition between s6-rc-init and s6-svscan. The context: as a concrete project to test s6-rc, I am using it to manage my X session, mainly for setup and supervising background tasks. So I want s6-svscan to be the "r