Description of problem:

This awfully weird. iptables-save will, as expected, dump the current firewall rules to stdout. However, I get an empty file when I try to redirect that output to a file. I'm doing this as root, I'm not overwriting an existing file, the filesystem is not full.

If I pipe the output of iptables-save through cat first, the result makes it to the file:

[root@test sysconfig]# iptables-save | cat >foo

This happens on both of my 64-bit F10 systems, but not on my 32-bit systems.


Version-Release number of selected component (if applicable):

iptables-1.4.1.1-2.fc10.x86_64

How reproducible:

Always, on 64-bit systems.


Steps to Reproduce:
1. iptables-save
2. iptables-save >foo
  
Actual results:

foo is an empty file, instead of containing the output of iptables-save


Expected results:

foo should contain the output you'd get from running iptables-save