66 is a wrapper around s6-rc which brings some very good enhancements, eg
declarative service frontend files (similar to systemd unit files), & neater
organisation of service bundles/runlevels (called trees).
A good read in regards to 66 service frontend (unit) files can be found here
For anybody interested on s6-rc/s6-66 on Debian based distro's I have created
some unofficial spins with multiple inits which work independently from each
other.
The concept is very simple, any init can be installed under a /usr/lib folder,
their service files in relevant sub-folders under
Check out Artix Linux for a traditional Linux distribution that uses s6
[1]. The s6-scripts link might be the most useful to you, as it's the
"nitty-gritty" (PID 1 initialization and basic daemons).
Laurent is involved in s6-overlay [2], which is geared towards containers
but provides a lot of
Hey Group,
I'm building a Linux system based on musl and Busybox. I'm considering
using s6/s6-rc as an init/supervision system. I see there are good docs
on all the skanet.org programs, but I can't find an example of a working
configuration that puts them together. Is there an example
I have been using `--print-pid=3` as readiness notification for dbus-daemon
for quite a while now on my user services and I haven't had any problems
with it so far. IIRC, looking at dbus-daemon code, it actually prints the
socket address first then its pid. So, I use the `--print-address=` option
On Sat, Apr 6, 2024, 19:43 Guillermo wrote:
> But then, there is a problem if one actually wants the server address
> information that --print-address provides. Alexis' 'run' script for
> example wants to save that to a file (apparently in a directory
> suitable for s6-envdir). If the output is
But then, there is a problem if one actually wants the server address
information that --print-address provides. Alexis' 'run' script for
example wants to save that to a file (apparently in a directory
suitable for s6-envdir). If the output is sent to the notification
pipe instead,
El mié, 3 abr 2024 a las 8:37, Laurent Bercot escribió:
>
> >2) The presence of a notification-fd file tells s6 that dbus-daemon
> >can be somehow coerced into producing an s6-style readiness
> >notification using file descriptor 3 without changing its code, are
> >you sure that's the case with
