Re: upstart: please update to latest upstream version
Vincent Bernat <firstname.lastname@example.org> writes:
> OoO Vers la fin de l'aprÃ¨s-midi du dimanche 11 mars 2012, vers 16:14,
> Fernando Lemos <email@example.com> disaitÂ :
>>> Maybe we could Â have an intermediate goal to patch any Â daemon to add an
>>> option Â to not Â fork on Â start. Â If Â any daemon Â can be Â started without
>>> forking, it seems Â easy to start/stop them without Â cgroups. Â This would
>>> allow to generate a sysvinit Â script from systemd service description. I
>>> don't Â know Â any daemon Â that Â does Â not have Â a Â flag Â to Â not fork Â on
>>> start. The number of daemons to patch may be low.
>>> This will not be Â as clean as using cgroups, but it Â won't be worst than
>>> the actual situation.
>> I don't quite understand the problem you're trying to solve. Both
>> upstart and systemd already handle cases where the daemon doesn't have
>> the option of not forking.
> Yes, but systemd relies on cgroups which are not portable. If all
> daemons were able to not fork, it would be easier to convert a .service
> file to a classic init.d script and therefore use systemd (for example)
> as default with Linux and sysvinit with autogenerated files on kFreeBSD.
That would actually make things more difficult since then you have to
add some delay into the sysvinit files to wait for the daemon to become
ready before the init.d script returns.
The only thing that would benefit would be to run systemd on kFreeBSD
without the cgroup mechanism. No forking so no need to trace fork()s.