Roger Oberholtzer wrote:
On Mon, 2011-07-18 at 11:21 +0200, Per Jessen wrote:
Roger Oberholtzer wrote:
IMO, the problem is ntp, not the system start stuff. Since I have effectively removed my network from the system startup environment, I would find it hard to see that environment being able to solve ordering or dependency issues. How could a system service know that some user will, via their own non-system configuration, eventually, maybe start a network where an interesting server lives?
A daemon would just try to reach the interesting server, and when the error says "network not reachable" (or something similar) it means it's still not there.
But how would a daemon know which network the interesting server is on? Perhaps a moot point. It could re-try each time the network configuration changed.
It doesn't care about the network config - for arguments sake, let's assume it uses TCP. In pseudo-code, you would issue a
connect(<desired server address>);
If the network is not available, the connect() does not succeed. This is no different to you trying to access an external website when your network is down. Slightly different for UDP, but essentially the same.
Of course. But, at some point in the future, will ntp retry to make the connection? On that point the jury is still out. You have presented evidence where it seems to. I have presented a counter claim that shows up in my usage. I suspect ntp does retry the connection when it does, and does not try again when it does not...
To stick to the legal metaphors, I think the judge will dismiss your claim as hear-say :-) At least until you present evidence that the server is configured but not used ("ntpq -p" will show the peers). -- Per Jessen, Zürich (18.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org