Re: Invoking ‘init’ from an init.d script (Wheezy)

On Wed, Jun 10, 2015 at 2:14 PM, David Kalnischkies wrote: > On Mon, Jun 08, 2015 at 12:09:37PM +0200, Alexander Thomas wrote: >> I know, but this is a closed system and nothing is pulled in from >> external repositories during this automated update. The stuff that is >>

Re: Invoking ‘init’ from an init.d script (Wheezy)

On Mon, Jun 8, 2015 at 11:49 AM, Ansgar Burchardt wrote: > Hi, > > On 06/08/2015 10:29 AM, Alexander Thomas wrote: >> We >> falsely assumed that setting DEBIAN_FRONTEND=noninteractive >> APT_LISTCHANGES_FRONTEND=none, and using the -y and --force-yes >> opt

Re: Invoking ‘init’ from an init.d script (Wheezy)

On Fri, Jun 5, 2015 at 7:39 PM, Konstantin Khomoutov wrote: > On Fri, 5 Jun 2015 16:25:21 +0200 > Alexander Thomas wrote: > > [...] >> That would be an option, but it might still cause the same problem of >> apt-get hanging as we currently experience when doing the upd

Re: Invoking ‘init’ from an init.d script (Wheezy)

On Wed, Jun 3, 2015 at 6:09 PM, Konstantin Khomoutov wrote: > > On Wed, 3 Jun 2015 17:26:21 +0200 > Alexander Thomas wrote: > > [...] > > The long story: > > > > We have a setup with multiple servers (running Wheezy). When booting, > > the servers check wh

Invoking ‘init’ from an init.d script (Wheezy)

7;re doing might not be perfectly sane and wonder whether it might have other risks. We could avoid this 'init-inside-an-initscript' hack if someone had a foolproof way of guaranteeing that the init script is always executed as the very first in runlevel 2. -- Alexander Thomas -- To UNSU