[snip from a restart] Activating Rules... Processing /etc/shorewall/start ... Shorewall Restarted touch: creating `/var/state/shorewall'': No such file or directory curtain:~# dpkg -l | grep shorewall ii shorewall 1.3.7c Shoreline Firewall (Shorewall) Cant find anything in the errata.. seems to point at the wrong semaphore file?
On Sat, 7 Sep 2002, j2 wrote:> [snip from a restart] > > Activating Rules... > Processing /etc/shorewall/start ... > Shorewall Restarted > touch: creating `/var/state/shorewall'': No such file or directory > curtain:~# dpkg -l | grep shorewall > ii shorewall 1.3.7c Shoreline Firewall (Shorewall) > > > Cant find anything in the errata.. seems to point at the wrong semaphore > file? >I''m not where I can access a Debian box -- check shorewall.conf though; I suspect that STATEDIR is being set differently than in prior versions. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net
> I''m not where I can access a Debian box -- check shorewall.conf though; I > suspect that STATEDIR is being set differently than in prior versions.Its set like this # Set this to the name of the lock file expected by your init scripts. For # RedHat, this should be /var/lock/subsys/shorewall. On Debian, it # should be /var/state/shorewall. If your init scripts don''t use lock files, # set -this to "". # SUBSYSLOCK=/var/state/shorewall # This is the directory where the firewall maintains state information while # it is running # STATEDIR=/var/lib/shorewall so which is the right "debianized" way?
On Sun, 8 Sep 2002, j2 wrote:> > I''m not where I can access a Debian box -- check shorewall.conf though; I > > suspect that STATEDIR is being set differently than in prior versions. > > Its set like this > > # Set this to the name of the lock file expected by your init scripts. For > # RedHat, this should be /var/lock/subsys/shorewall. On Debian, it > # should be /var/state/shorewall. If your init scripts don''t use lock files, > # set -this to "". > # > > SUBSYSLOCK=/var/state/shorewall > > # This is the directory where the firewall maintains state information while > # it is running > # > > STATEDIR=/var/lib/shorewall > > > so which is the right "debianized" way? >I don''t know -- I don''t package the .deb and as I said in an earlier postk, I''m not near a Debian box (and won''t be until the middle of next week). I would assume that you could work around the problem by "mkdir /var/state" however... -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net