Starting shorewall

Paul Howarth paul at city-fan.org
Sun Apr 9 14:43:11 UTC 2006


On Sun, 2006-04-09 at 15:21 +0100, Timothy Murphy wrote:
> Paul Howarth wrote:
> 
> > Try editing /etc/rc.d/init.d/shorewall and changing the line:
> > # chkconfig: - 25 90
> > to
> > # chkconfig: - 55 90
> > 
> > Then do:
> > # chkconfig --del shorewall
> > # chkconfig --add shorewall
> > # chkconfig shorewall on
> > 
> > That should fix the position for all runlevels.
> 
> Thanks for your advice.
> This puts shorewall in a sensible position in /etc/rc.d/rc[35].d/
> (after my WiFi LAN has started),
> so that it seems to start correctly - no error is reported.
> 
> I've also turned iptables off.
> 
> However, shorewall still does not seem to work
> until I run "sudo service shorewall restart" after logging in.
> 
> As I said, this does not cause any difficulty,
> as I very rarely re-boot the machine.
> It simply causes puzzlement.

Strange indeed.

> I'm wondering if it could have anything to do with udev?
> The reason I ask is that I also have some mount commands in rc.local ,
> 
> /bin/mount /dev/hda1 /www
> /bin/mount /dev/hda2 /martha
> /bin/mount /dev/hda3 /elizabeth
> /bin/mount /dev/hda5 /alfred
> 
> and these also fail, with the statement that these devices do not exist,
> although exactly the same commands work (as superuser)
> once I have logged in.

Is there some reason you don't just put entries for these in /etc/fstab
and have them mounted along with all the other filesystems?

Paul.




More information about the fedora-list mailing list