On Tuesday 01 June 2004 14:54, Praveen wrote:
R Deepak wrote:
Is this even possible under normal circumstances? I've never ever seen a
system which did not have lo up and running.
I came across this problem in my Debian Woody box two years ago. The
reason was that 'lo' was not up. See some pointers below.
But, I've seen this error a lot when there is heavy portscan traffic on
I don't deny that there may be other problems that causes this one. Some
(look into the follow-ups as well)