A bug I ran in to the other day when a remote site fell out of DNS
(read: someone wasn't smart enough to setup a reliable secondary, ala
Microsoft some number of years ago).
I've yet to dig through code to see if I can easily patch it...
----- Forwarded message from Russell Van Tassell <russell at loosenut com> -----
Date: Mon, 10 Nov 2003 10:17:02 -0800
From: Russell Van Tassell <russell at loosenut com>
To: snips-bugs at navya com
Subject: Portmon breaks with unknown host
Looks like portmon breaks if you give it an unknown host, causing false
alerts on all subsequent entries in the config file... portmon.error
shows something to the effect of:
inet_addr() failed for www.somewebsite.com: Error 0
www.somewebsite.com is unknown host
Config file entry would be something like:
HOST www-sws www.somewebsite.com HTTPport 80 Critical GET http://www.somewebsite.com/ HTTP/1.0\r\n
info <HEAD>
...commenting out the entry and HUP'ing portmon allows all the other
alerts to return to normal. Portmon should be better at detecting
problems in the config (such as unresolveable hosts) and ignore them (or
immediately bump them to critical).
Russell
--
Russell M. Van Tassell
russell at loosenut com
"So if Windows on Intel is Wintel, would UNIX on Intel be UnIntel?"
- grant at cscorp com 2002/02/22 16:18 PST
----- End forwarded message -----
--
Russell M. Van Tassell
russell at loosenut com
Q: Why do ducks have flat feet? Q: Why do elephants have flat feet?
A: To stamp out forest fires. A: To stamp out flaming ducks.
|