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
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
Thanks for your advice and help.
> On Apr 6, 2024, at 19:00, Laurent Bercot wrote:
>
> - removing all the other files than the sources.
> - making a suitable unit file to start s6-svscan.
> - taking advantage of the fact that systemd, unlike openrc, has a logging
> mechanism, so you don't need
One last question: do we need the s6-openrc rpm package? I know systemd is more
popular for Redhat and Fedora. Any suggestion?
I doubt anyone is going to run openrc on Fedora. If you're going to
package
s6 for a given distribution, you should integrate it properly with that
distribution,
Currently, s6 rpm packages is almost done, except s6-openrc package, all the
other s6 rpm package has the same contents as the alpine package. There is also
some point I need help from this mail list:
1. Try to verify pre-install and pre-upgrade script works for s6 rpm packages.
2. Try to
Let me check the alternatives system first.
> On Apr 4, 2024, at 01:08, Laurent Bercot wrote:
>
> Then it looks like the correct way to proceed, if Eric can coordinate with
> the maintainers of the filesystem and bash packages.
