On Monday 28 November 2005 18:19, Mike McMullin wrote: <snippage>
I expected YaST to have control of the daemon(s). My expectations of what YaST should have done, and what it did are differing. Again from CLI it worked from YaST it reported a failure.
Hi Mike & All... FWIW, I always got the NTP client in 9.2, 9.3 and 10.0 working like this: a) YaST CC -> Network Services -> NTP Client module. b) enter my preferred time server c) click 'test' and it fails. d) switch to YaST CC -> System -> Run Level Editor e) drop the firewall f) 'test' in the NTP Client module succeeds this time g) just accept the defaults and the NTP Client module will close h) restart the firewall i) NTP syncs and works just fine after this (for me, YMMV etc etc.) I only do step 'c' above because I can never remember if it's necessary to drop the firewall when configuring the client. My take on this is that the client config module must be poking any needed holes in the firewall. regards, - Carl