Hi Jonathan,
On Sat, May 10, 2014 at 02:16:25PM +0100, Jonathan Wiltshire wrote:
> Control: severity -1 serious
>
> Hi,
>
> On Wed, May 07, 2014 at 06:20:02PM +0100, Jakub Warmuz wrote:
> > Unfortunately, I'm *unable to boot* the system with
> > netfilter-persistent systemd service enabled!
> >
Package: iptables-persistent
Followup-For: Bug #665720
Thanks, works for me now :)
signature.asc
Description: OpenPGP digital signature
Control: severity -1 serious
Hi,
On Wed, May 07, 2014 at 06:20:02PM +0100, Jakub Warmuz wrote:
> Unfortunately, I'm *unable to boot* the system with
> netfilter-persistent systemd service enabled!
>
> Removing "quiet" from the kernel parameters, reveals that it hangs
> with the following message
Package: iptables-persistent
Version: 1.0
Followup-For: Bug #665720
Dear Maintainer,
Unfortunately, I'm *unable to boot* the system with
netfilter-persistent systemd service enabled!
Removing "quiet" from the kernel parameters, reveals that it hangs
with the following message displayed in a loop
Forgot to mention in my last mail how to use it as an user:
systemctl daemon-reload
systemctl start iptables-persistent.service
systemctl enable iptables-persistent.service
The last line is used to have it activated in future boots.
signature.asc
Description: This is a digitally signed message p
I added a small systemd unit file to avoid this bug. The unit file is
unconventional, as it calls the shell script instead of replacing it. Note,
that my experience with systemd is quite limited.
The systemd unit file contains the following:
[Unit]
Description=Loads iptables rules from /etc/ipt
Package: iptables-persistent
Version: 0.5.3
Severity: important
Iptables rules are not restored on startup with systemd because of an ordering
cycle:
[3.493400] systemd[1]: Found ordering cycle on basic.target/start
[3.494481] systemd[1]: Walked on cycle path to sysinit.target/start
[
7 matches
Mail list logo
