On Mon, Aug 15, 2016 at 07:08:09PM +0200, Laurent Bercot wrote: > 1. Would you happen, by any chance, to have a longrun, in your service > database, named s6-svscan-log? If you do, rename that service to something > else: it conflicts with the catch-all logger that is managed by s6 but not > bys6-rc.
Actually I deviated from the `s6-svscan-log' name, and chose `s6-svscan.log' due to personal peference; nevertheless, I can confirm that there is no s6-rc service definition directory named `s6-svscan.log', `s6rc-fdholder' or `s6rc-oneshot-runner'. > 2. What is the s6-svscan-log run script? A verbatim copy follows (/bin/rc is a Unix port of Plan 9's rc(1), and can be installed as the `rc' package from Alpine's testing repository): > #!/bin/rc > exec \ > redirfd -rnb 0 fifo \ > redirfd -w 1 /dev/console \ > fdmove -c 2 1 \ > s6-setuidgid nobody \ > emptyenv -p \ > s6-log -bp t T /run/uncaught-logs > 3. Do you have anything else in the service directory? There is only the `run' script, no more and no less; the creation of `fifo' in tmpfs is arranged in the stage1 script (objects, that are not files, directories or links, in /etc are sometimes really annoying for the sysadmin :(). -- My current OpenPGP key: RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19) 7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C
