RESENTs after up

[Michael Costello]

I am having a problem with Argus v3.4 in which notifications are sent
even after the object comes up.

Here, a test object is down, then comes up, then has two more down
notifications sent.  Renotify is set to 5 minutes.  Clocks are
syncrhonized.  Escalations are also resent after the object comes up.

(from root at localhost)	by bar (8.13.3/8.13.3/Submit) id
jA6Jqai9035633;	Sun, 6 Nov 2005 14:52:36 -0500 (EST)	(envelope-from
root)

49867 Top:foo:Servers:dummy:Ping_1.2.3.4 is DOWN - 06/Nov 14:37


(from root at localhost)	by bar (8.13.3/8.13.3/Submit) id
jA6JsaEo035675;	Sun, 6 Nov 2005 14:54:36 -0500 (EST)	(envelope-from
root)

49868 Top:foo:Servers:dummy:Ping_1.2.3.4 is UP - 06/Nov 14:53


(from root at localhost)	by bar (8.13.3/8.13.3/Submit) id
jA6JvaPk035728;	Sun, 6 Nov 2005 14:57:36 -0500 (EST)	(envelope-from
root)

49867 Top:foo:Servers:dummy:Ping_1.2.3.4 is DOWN - 06/Nov 14:37


(from root at localhost)	by bar (8.13.3/8.13.3/Submit) id
jA6K2ast035820;	Sun, 6 Nov 2005 15:02:36 -0500 (EST)	(envelope-from
root)

49867 Top:foo:Servers:dummy:Ping_1.2.3.4 is DOWN - 06/Nov 14:37