Am 08.09.2010 16:02, schrieb Gustavo Sverzut Barbieri:
> Since you're doing this approach that would require an extra step, why
> not aim at a more powerful script that converts them to systemd units?
> Many of scripts these days use start-stop-daemon and we could generate
> matching units without
.d files, but i am of course open for suggestions.
Regards,
Reno Reckling
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Am 10.08.2010 13:34, schrieb Graham Cantin:
> Nope, I think they solved the goal you mentioned first -- executing a
> frontend shell script while the system is up and running to parse run
> dependencies is much different than bash(1) running *during* init.
Nevertheless, if you look at /etc/init.d/
Am 10.08.2010 02:57, schrieb James Cloos:
> The runscript(8) src might provide useful clues.
Hi James,
i just took a look at the runscript code to generate the deptree, the comment
looks like that:
/* This is a 6 phase operation
Phase 1 is a shell script which loads each init script and conf
doing this, because bash
depends on systemds functionality?
Regards,
Reno Reckling
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
