Mark Elsen wrote: >That may not be enough in a context where the Firewalling software was >started and then stopped. Residual rules and or states may still affect the >loopback interface. > >Can you, for instance, 'ping localhost' with success ? > > Yup... Even with the firewall up and running: [root@localhost bin]# ping localhost PING localhost.localdomain (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=0 ttl=64 time=0.339 ms 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.260 ms 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=2 ttl=64 time=0.260 ms 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=3 ttl=64 time=0.261 ms 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=4 ttl=64 time=0.251 ms 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=5 ttl=64 time=0.260 ms 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=6 ttl=64 time=0.252 ms --- localhost.localdomain ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6008ms rtt min/avg/max/mdev = 0.251/0.269/0.339/0.028 ms, pipe 2 > Set the firewalling functions off , wherever this needs to be done, > and *restart* the system. > Check whether you can ping the localhost (itself). > > > I haven't tried restarting yet - but given that "ping localhost" works with the firewall(s) in place do you still think that this is my problem? I still think that the "Permission denied" message is caused by file ownership problems - but where? Thanks Mark
Attachment:
signature.asc
Description: OpenPGP digital signature
