`/var/lock/subsys/bastille-firewall': No such file or directory

[PermaNoob]

When I restart bastille, I get:

Setting up IP spoofing protection... done.
Allowing traffic from trusted interfaces... done.
Setting up chains for public/internal interface traffic... done.
Setting up general rules... done.
Setting up outbound rules... done.
touch: cannot touch `/var/lock/subsys/bastille-firewall': No such file or directory
-----------------

There is no subsys directory--is that a problem?

[PermaNoob]

A related question:

I was thinking of installing APF firewall http://www.rfxnetworks.com/apf.php which I've been using for some time on my other server, but I wonder if I might run into any problems using it with ISPConfig?

I like APF because it makes it easy to ban ip's and automatically ban's ip's of anyone trying brute force and stops dos attacks.

[till]

You can use any firewall with ISPConfig, just make sure that you disabled the ISPConfig firewall before you install another one.

[PermaNoob]

You can use any firewall with ISPConfig, just make sure that you disabled the ISPConfig firewall before you install another one.

And I do that by just unchecking firewall in the ISPConfig admin or is there something else I need to do?

[PermaNoob]

And I do that by just unchecking firewall in the ISPConfig admin or is there something else I need to do?

Till or someone can answer that please?

Also, if I don't change from bastille, is

touch: cannot touch `/var/lock/subsys/bastille-firewall': No such file or directory

a problem?

[martinfst]

Just unchecking the tickbox is fine. Actually it's even not checked in the first place right after your initial installation. I have Shorewall running nicely alongside with ISPConfig.

[falko]

touch: cannot touch `/var/lock/subsys/bastille-firewall': No such file or directory

a problem?
You can get rid of that message by running
mkdir /var/lock/subsys/