Re: not starting a daemon upon installation

2020-03-09 Thread jnqnfe
On Sun, 2020-03-08 at 11:44 -0400, Marvin Renich wrote: > * jnq...@gmail.com [200308 10:58]: > > On Sat, 2020-03-07 at 21:30 +0100, Tomas Pospisek wrote: > > > The problem is that installing the package will automatically > > > start > > > the > > > daemon cluster in a "default" configuration. > >

Re: not starting a daemon upon installation

2020-03-09 Thread Marvin Renich
* jnq...@gmail.com [200308 10:58]: > On Sat, 2020-03-07 at 21:30 +0100, Tomas Pospisek wrote: > > The problem is that installing the package will automatically start > > the > > daemon cluster in a "default" configuration. > > > > [1] > > https://askubuntu.com/questions/74061/install-packages-wit

Re: not starting a daemon upon installation

2020-03-08 Thread jnqnfe
On Sun, 2020-03-08 at 18:50 +0100, Marc Haber wrote: > debootstrap's files don't contain the string "divert". They do, > however, dump "exit 101" to $TARGET/usr/sbin/poliy-rc.d. I should issue a small correction to my earlier statement of live-build using a dpkg-divert of start-stop-daemon as its

Re: not starting a daemon upon installation

2020-03-08 Thread Tomas Pospisek
On 07.03.20 21:30, Tomas Pospisek wrote: > tldr: why is not having a daemon started on install so involved? Can't > there be a better way? to which Jonas, Marco & jnqnfe replied (see thread). Thanks a lot Jonas, Marco & jnqnfe! *t

Re: not starting a daemon upon installation

2020-03-08 Thread jnqnfe
On Sun, 2020-03-08 at 18:50 +0100, Marc Haber wrote: > On Sun, 08 Mar 2020 14:58:01 +, jnq...@gmail.com wrote: > > how live-build achieves this is essentially the same as happens to > > be > > discussed in the linked page for Debian's debootstrap package (the > > tool > > for building the base

Re: not starting a daemon upon installation

2020-03-08 Thread Marc Haber
On Sun, 08 Mar 2020 14:58:01 +, jnq...@gmail.com wrote: >fyi, preventing start/stop of _all_ services on package installation is >a requirement of Debian's live-build, which if you're not familiar with >it is a tool to build a Debian live-cd. Building a live environment is >typically done in a

Re: not starting a daemon upon installation

2020-03-08 Thread jnqnfe
On Sat, 2020-03-07 at 21:30 +0100, Tomas Pospisek wrote: > The problem is that installing the package will automatically start > the > daemon cluster in a "default" configuration. > > That's a problem for me because etcd differentiates between starting > the > cluster for the first time and starti

Re: not starting a daemon upon installation

2020-03-08 Thread Marc Haber
On Sat, 7 Mar 2020 21:30:33 +0100, Tomas Pospisek >When I duckduckgo "dpkg do not start service on install" first hit is >[1] which contains /absurdly involved/ suggestions to achieve "not >starting a daemon upon installation". > >[1] >https://askubuntu.com/questions/74061/install-packages-without

Re: not starting a daemon upon installation

2020-03-08 Thread Marc Haber
On Sat, 7 Mar 2020 23:02:23 +0100, Marco d'Itri wrote: >There is: > ># systemctl mask $DAEMON.service ># apt install $DAEMON > >That's it. If the package fails to install then file a bug. For that you need to know how the $DAEMON is called. Greetings Marc --

Re: not starting a daemon upon installation

2020-03-07 Thread Marco d'Itri
On Mar 07, Tomas Pospisek wrote: > tldr: why is not having a daemon started on install so involved? Can't > there be a better way? There is: # systemctl mask $DAEMON.service # apt install $DAEMON That's it. If the package fails to install then file a bug. > When I duckduckgo "dpkg do not start

Re: not starting a daemon upon installation

2020-03-07 Thread Jonas Smedegaard
Quoting Tomas Pospisek (2020-03-07 21:30:33) > tldr: why is not having a daemon started on install so involved? Can't > there be a better way? > It /seems/ that the "official" way to achieve "not starting a daemon > upon installation" is to use `dpkg-divert` to overwrite `policy-rc.d` > with a