I wrote (on 20 Feb 2002 at 13:08):
Karl E. Jorgensen wrote (on 20 Feb 2002 at 9:57):
On Wed, Feb 20, 2002 at 09:13:47AM +0100, Tony Crawford wrote:
Hi Gang! [...] Running iptables -L by hand, I see that
it's very slow. It takes a minute or two to read out the FORWARD
chain in
On Wed, Feb 20, 2002 at 03:16:15PM +0100, Tony Crawford wrote:
By experimenting, I found out that the long lookup occurred when my
iptables rules used a netmask that does not correspond to a known
subnet, namely 192.168.2.0/28 when the local network is
192.168.2.0/24. iptables was
* Tony Crawford ([EMAIL PROTECTED]) [020220 06:14]:
Meanwhile, while we're on the subject, is there a way I can make
cron (or run-parts or whoever) wait longer for the output before
timing out? Or maybe detach the process? Or is that a bad idea?
What if you had 2 separate jobs: one runs
Alan James wrote (on 20 Feb 2002 at 15:53):
On Wed, Feb 20, 2002 at 03:16:15PM +0100, Tony Crawford wrote:
By experimenting, I found out that the long lookup occurred
when my iptables rules used a netmask that does not correspond
to a known subnet, namely 192.168.2.0/28 when the local
4 matches
Mail list logo
