On Mon, Aug 19, 2019 at 11:55:13AM -0400, Sam Hartman wrote:
> Enrico> Those packages that use more unit file features can still
> Enrico> ship an init.d script, but at least all those packages that
> Enrico> just start/stop a service don't need to bother about
> Enrico>
Hi,
On Mon, Aug 19, 2019 at 09:55:22PM +0300, Andrei POPESCU wrote:
> > I hope we also support the case where we ship a restricted unit file for
> > non-systemd and a unrestricted unit file for systemd.
> Would there be cases where the "restricted" unit file is using options
> not present in
On Lu, 19 aug 19, 11:55:13, Sam Hartman wrote:
>
> I hope we also support the case where we ship a restricted unit file for
> non-systemd and a unrestricted unit file for systemd.
Would there be cases where the "restricted" unit file is using options
not present in the "unrestricted" unit file,
> "Enrico" == Enrico Zini writes:
Enrico> Those packages that use more unit file features can still
Enrico> ship an init.d script, but at least all those packages that
Enrico> just start/stop a service don't need to bother about
Enrico> maintaining yet another shellscript
Hi,
On Thu, Aug 15, 2019 at 02:49:32PM +0200, Vincent Bernat wrote:
> > So we might have to invent magic comments still and/or convinve systemd
> > people that it might be a good idea to have unit files that can support
> > both immediate and on-demand start.
> It's already the case. Require
❦ 15 août 2019 14:11 +02, Simon Richter :
> So we might have to invent magic comments still and/or convinve systemd
> people that it might be a good idea to have unit files that can support
> both immediate and on-demand start.
It's already the case. Require the socket for on-demand start,
Hi,
On Thu, Aug 15, 2019 at 10:40:22AM +0200, Enrico Zini wrote:
> [changed subject because I can't stand the old one]
Good idea.
> Alternatively, we can decide on a subset of unit files that would cover
> the normal start-stop-daemon features, and like 80% of initscripts, and
> would be very
7 matches
Mail list logo
