On Thu, Apr 27, 2023 at 10:54:58AM +0200, Marc Haber wrote:
> On Thu, 27 Apr 2023 08:20:34 +0200, Simon Richter
> wrote:
> >On Wed, Apr 26, 2023 at 04:25:19PM +0200, Marc Haber wrote:
> >> I am not sure whether it is doing non-systemd users a favor to keep a
> >> probably outdated, bitrotting and
On Thu, 27 Apr 2023 08:20:34 +0200, Simon Richter
wrote:
>On Wed, Apr 26, 2023 at 04:25:19PM +0200, Marc Haber wrote:
>> I am not sure whether it is doing non-systemd users a favor to keep a
>> probably outdated, bitrotting and untested init script in the
>> canonical place. My gut feeling is that
On Thu, Apr 27, 2023 at 09:02:38AM +0800, Paul Wise wrote:
> On Wed, 2023-04-26 at 22:44 +0300, Boian Bonev wrote:
>
> > OTOH it is an un-favor to move or remove it
> ...
> > It is better to keep the init script in place.
Absolutely.
> Another option is the orphan-sysvinit-scripts package:
Whic
Hi,
On Wed, Apr 26, 2023 at 04:25:19PM +0200, Marc Haber wrote:
> I am not sure whether it is doing non-systemd users a favor to keep a
> probably outdated, bitrotting and untested init script in the
> canonical place. My gut feeling is that it might be better to ship the
> old init script in /us
On Wed, 2023-04-26 at 22:44 +0300, Boian Bonev wrote:
> OTOH it is an un-favor to move or remove it
...
> It is better to keep the init script in place.
Another option is the orphan-sysvinit-scripts package:
Description: Orphaned System-V-like init scripts
This package provides System-V init sc
Hi,
On Wed, 2023-04-26 at 16:25 +0200, Marc Haber wrote:
> On Mon, 24 Apr 2023 15:48:02 +0100, Matthew Vernon
> wrote:
> > One thing I'd say is: please keep the init script in your package,
> > so that people using inits other than systemd can continue to use
> > it.
>
> I am not sure whether it
On Mon, 24 Apr 2023 15:48:02 +0100, Matthew Vernon
wrote:
>One thing I'd say is: please keep the init script in your package, so
>that people using inits other than systemd can continue to use it.
I am not sure whether it is doing non-systemd users a favor to keep a
probably outdated, bitrotting
Hi,
Perry Naseck writes:
> I am in the process of updating/upgrading a package from an init.d service
> to a Systemd service. Are there any recommended guidelines for this process?
>
> Looking through some current packages I see that a lot of them have both an
> init script and a Systemd service
On 4/20/23 14:48, Perry Naseck wrote:
Hello!
I am in the process of updating/upgrading a package from an init.d
service to a Systemd service. Are there any recommended guidelines for
this process?
My generic advice would be: start your thinking from a perspective of
"how should this work in
Hello!
I am in the process of updating/upgrading a package from an init.d service
to a Systemd service. Are there any recommended guidelines for this process?
Looking through some current packages I see that a lot of them have both an
init script and a Systemd service in their debian folder. Do
d
10 matches
Mail list logo
