Replying to my own post :)The problem was that my ntp server was only allowing query connections from localhost and not my internal network (default Debian configuration)
So ntptrace localhost worked but not ntptrace my.machine.nameHowever servers further up the chain still time out sometimes (presumably because I'm using pool.ntp.org and some allow queries and not others). Bigsister doesn't seem to care as long as the monitored host gives a valid reply.
BUT: in this case what's the point of doing a ntptrace rather than a ntpdate? To me it only seems to add extra load to all the servers. But then I don't know much about NTP... Martin ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Bigsister-general mailing list suppressed https://lists.sourceforge.net/lists/listinfo/bigsister-general
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.