-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/20/2013 02:02 PM, Betsy Schwartz wrote:
Also, the second or third time, I just set the alert out quite a
ways, like disable until February 2014, and I noticed xymon
reports funky dates like the one below… Disabled until Tue Oct
19 07:48:44 1926 Is this a known bug with xymon in this verison?
I've seen that too, and I do think it's a bug, but I haven't seen
it with 2014. In our version (4.3.10 on RHEL5) the disable works
up to 8404 weeks. Enter 9999 weeks,you get a date in the past
I used to run the Xymon display on IRIX and found that even 999 weeks
was too far in the future and would roll over. I'm guessing this is
less a bug and more an operating system limitation (though this should
probably behave by setting it as late as possible, not by rolling over
- -- maybe that's not possible).
- --
- ---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlElIEkACgkQmb+gadEcsb5BFgCgnFyR4U3ypwbjrtMqiytBxWaV
4CQAnAhlD+4EL3V9b3MyOY2cI+msW+3/
=MrAP
-----END PGP SIGNATURE-----