> I think you misunderstand. I think you're missing the point.
> IF you have http already listening on the address you serve NTP from,
> then there MUST be a redirect from pool.ntp.org to www.pool.ntp.org.
>
> IF you do not have http running, then there IS NOTHING TO DO.
As I said, you are making assumptions about the way we run our machines. You
are assuming that when our port-80 server says "apache" it is telling the
truth; and even if it is now, there's no reason why it should continue to
be. You are assuming that there is actually one machine answering for our
timeserver addresses. You are assuming that we configure our machines by
hacking on local configuration files. You are assuming that we would be
happy to have our future plans constrained. And so on...
As I said, if the project decides to impose constraints on other services
which our timeserver addresses respond to then we'll simply decide to leave
the pool. I expect the addresses which are currently in the pool will
continue to respond to NTP. I would be surprised if we're the only large
site to think that way.
--
Dr George D M Ross, School of Informatics, University of Edinburgh
Kings Buildings, Mayfield Road, Edinburgh, Scotland, EH9 3JZ
Mail: [EMAIL PROTECTED] Voice: +44 131 650 5147 Fax: +44 131 667 7209
PGP: 1024D/AD758CC5 B91E D430 1E0D 5883 EF6A 426C B676 5C2B AD75 8CC5
pgpeavEr9P1rJ.pgp
Description: PGP signature
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
