Am 09.07.2014 16:45, schrieb Stefano Zacchiroli:
> On Wed, Jul 09, 2014 at 02:04:49PM +0200, Michael Biebl wrote:
>> What's the output of
>> ls -la /etc/rc?.d/???shorewall
>> and
>> ls -la /etc/rc?.d/???shorewall6
>
> $ ls -la /etc/rc?.d/???shorewall
> lrwxrwxrwx 1 root root 19 apr 27 15:43
On Wed, Jul 09, 2014 at 02:04:49PM +0200, Michael Biebl wrote:
> What's the output of
> ls -la /etc/rc?.d/???shorewall
> and
> ls -la /etc/rc?.d/???shorewall6
$ ls -la /etc/rc?.d/???shorewall
lrwxrwxrwx 1 root root 19 apr 27 15:43 /etc/rc0.d/K01shorewall ->
../init.d/shorewall
lrwxrwxrwx
Am 09.07.2014 13:51, schrieb Stefano Zacchiroli:
> I've tried this, and it does make the boot complete successfully.
> However, as a consequence, the shorewall service is not running after
> boot (because for some reason it fails to properly start the first
> time), and will never be running again
Thanks for your analysis, it explains what's happening.
On Wed, Jul 09, 2014 at 01:18:33AM +0200, Michael Biebl wrote:
> Am 09.07.2014 01:14, schrieb Michael Biebl:
> > So, what to do about this: I'd say it's a bug to (re)start a SysV init
> > script from an if-up.d hook without actually checking
Am 09.07.2014 01:28, schrieb Michael Biebl:
> Running within the context of an if-up.d hook you make an explicit
> assumption that $network is already provided, which is probably reasonable.
>
> Strictly speaking though, the LSB $network facility is defined in
> /etc/insserv.conf when the network
Am 09.07.2014 01:14, schrieb Michael Biebl:
> Am 08.07.2014 22:50, schrieb Stefano Zacchiroli:
>> Now the questions/comments:
>>
>> - I've had that script since ever, basically, and it used to work fine
>> in the past, both before and after switching to systemd as init. I'm
>> not sure why/when
Am 09.07.2014 01:14, schrieb Michael Biebl:
> So, what to do about this: I'd say it's a bug to (re)start a SysV init
> script from an if-up.d hook without actually checking if the service is
> actually already runnig.
> Because you simply disregard any dependencies which have been specified
> in th
Am 08.07.2014 22:50, schrieb Stefano Zacchiroli:
> Now the questions/comments:
>
> - I've had that script since ever, basically, and it used to work fine
> in the past, both before and after switching to systemd as init. I'm
> not sure why/when it stopped working.
>
> - As a mere user, the ab
On Tue, Jul 08, 2014 at 10:50:27PM +0200, Stefano Zacchiroli wrote:
> #!/bin/sh
[...]
> service $FIREWALL restart
> service $FIREWALL6 restart
>
>
> After a couple of killall local-firewall (one for each service
> invocation,
On Tue, Jul 08, 2014 at 09:32:43PM +0200, Michael Biebl wrote:
> Did you actually wait forever, i.e. at least 90 seconds which is the
> usual timeout for devices to appear or services to start?
Obviously I didn't wait *forever* :), but yes, I did wait past usual
network timeouts. To be sure, I've
Am 08.07.2014 21:20, schrieb Stefano Zacchiroli:
> Package: systemd
> Version: 204-14
> Severity: serious
>
> I've rebooted today my laptop (Debian testing) and it failed to boot, hanging
> forever on the message:
>
> [ *** ] A start job is running for LSB: Raise network interfaces.
Did you a
Package: systemd
Version: 204-14
Severity: serious
I've rebooted today my laptop (Debian testing) and it failed to boot, hanging
forever on the message:
[ *** ] A start job is running for LSB: Raise network interfaces.
with the 3 asterisks moving back and forth.
I've been using systemd-sysv
12 matches
Mail list logo
