(Normally Jonathan would be replying to this point, but I still do not
see him in this thread, so I rashly take this job ;)
On Mon, Jun 26, 2017 at 05:05:15PM +0200, Istvan Szukacs wrote:
> I understand that service files are much better that shell scripts
Actually they are not. This statement
Would
this approach keep systemd installed just to provide for services
directly
depending on it?
# rpm -q --requires openssh-server | grep systemd | sort -u
libsystemd.so.0()(64bit)
libsystemd.so.0(LIBSYSTEMD_209)(64bit)
systemd-units
I am not sure why any service would depend on these. Is
On Mon, Jun 26, 2017 at 04:02:47PM +0200, Istvan Szukacs wrote:
> Hi,
>
> I have a crazy question about s6. Would it be possible to make systemd
> compatible? This question might sound stupid at first but here is the
> reasoning:
>
> - we have services with systemd service files already
>
Hi Charles,
Yeah I can clarify. The only thing that I (or for that matter saner systems
engineers) want from systemd is to be a better sysv init. I do not want
logging, ntp and all the other crap that got sucked into it. I understand
that service files are much better that shell scripts and this
a bunch of hackers behind Void Linux[2] made everything tick on top of
runit without all that much effort.
The problem with the runit model is that it is pure supervision -
it does not provide service management. You have to run all your
oneshots _before_ you can start longruns. See
Could you be more clear about what you mean by "make systemd compatible"?
Do you mean loading systemd configuration files into s6, or the reverse?
The former strikes me as exceedingly difficult to implement in a complete
and correct manner.
One of the things that makes systemd so...
Hi Istvan,
check out nosh[1]. It explicitly states systemd compat as one of its
goals and goes to great lenghts to make it happen.
[1]: https://jdebp.eu/Softwares/nosh/
It preserves the daemontools style and spirit.
Meanwhile, while hordes of programmers are busy making everything fit
into the
Hi,
I have a crazy question about s6. Would it be possible to make systemd
compatible? This question might sound stupid at first but here is the
reasoning:
- we have services with systemd service files already
(/etc/systemd/system/*.service, etc.)
- the previous alternatives all failed to gain
