I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server. Addresses are provided by YaST's NTP Client module. Has anyone success in setting up 10.0 with a N.A. time server?
* Mike McMullin <mwmcmlln@mnsi.net> [11-27-05 04:04]:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server.
instead of direct addresses, try ca.pool.ntp.org or us.pool.ntp.org, ie: ca.pool.ntp.org ca.pool.ntp.org ca.pool.ntp.org ca.pool.ntp.org ca.pool.ntp.org in your /etc/ntp.conf file. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2005-11-27 at 04:01 -0500, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server.
Did you remember to open the appropriate port in the firewall? FW_SERVICES_EXT_UDP="ntp" - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDiaYQtTMYHG2NR9URAlTuAJ9HVMU978NZ6ZR/v3rlu6iOzSq3TQCfToyZ um3OwpYO2TyH8V5N99xLuNE= =bMoq -----END PGP SIGNATURE-----
On Sunday 27 November 2005 13:26, Carlos E. R. wrote:
The Sunday 2005-11-27 at 04:01 -0500, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server.
Did you remember to open the appropriate port in the firewall?
FW_SERVICES_EXT_UDP="ntp"
And if it is already open in the SuseFW, if you have any NAT or filter elsewhere, remember that NTP needs to be open in *both* directions. -- Bjørge
On Sun, 2005-11-27 at 13:26 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2005-11-27 at 04:01 -0500, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server.
Did you remember to open the appropriate port in the firewall?
FW_SERVICES_EXT_UDP="ntp"
I haven't done much with the Firewall at all, so I'm not sure where to make that change. Could you help me on that one? Mike
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2005-11-27 at 21:48 -0500, Mike McMullin wrote:
Did you remember to open the appropriate port in the firewall?
FW_SERVICES_EXT_UDP="ntp"
I haven't done much with the Firewall at all, so I'm not sure where to make that change. Could you help me on that one?
Assuming you are using the default SuSEfirewall2, edit as root the file '/etc/sysconfig/SuSEfirewall2', find the line containing 'FW_SERVICES_EXT_UDP', and add 'ntp' to the right hand side, as above. Finally, run "rcSuSEfirewall2 reload". Notice that if you have a router-firewall, you will have to open that port there as well. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDiv+mtTMYHG2NR9URApN4AJ0ULgBE3gpyFj0pZCH43cbYUARolwCdEmiQ pqSXw9N3eHDXyRl3k70JXro= =ZNue -----END PGP SIGNATURE-----
On Sun, 2005-11-27 at 21:48 -0500, Mike McMullin wrote:
On Sun, 2005-11-27 at 13:26 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2005-11-27 at 04:01 -0500, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server.
Did you remember to open the appropriate port in the firewall?
FW_SERVICES_EXT_UDP="ntp"
I haven't done much with the Firewall at all, so I'm not sure where to make that change. Could you help me on that one?
Mike
Why would there be a need to open the port on the -client-? You only need to open the port on the firewall if you are acting as a server with other computers needing to connect to you. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2005-11-28 at 15:00 -0500, Ken Schneider wrote:
Why would there be a need to open the port on the -client-? You only need to open the port on the firewall if you are acting as a server with other computers needing to connect to you.
Because it doesn't work. Try. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDi28WtTMYHG2NR9URAl5hAJ9d+5cERKt+3gQCuPj+/N7RQQBwtQCfZjya hY8D9cCIayZFhYyURncWyTA= =DXpP -----END PGP SIGNATURE-----
On Monday 28 November 2005 03:56 pm, Carlos E. R. wrote:
The Monday 2005-11-28 at 15:00 -0500, Ken Schneider wrote:
Why would there be a need to open the port on the -client-? You only need to open the port on the firewall if you are acting as a server with other computers needing to connect to you.
Because it doesn't work. Try.
Then there must be a problem with the firewall.... I've never had to open ports for NTP and no routers do either that I am aware of.
On Monday 28 November 2005 23:39, Bruce Marshall wrote:
On Monday 28 November 2005 03:56 pm, Carlos E. R. wrote:
The Monday 2005-11-28 at 15:00 -0500, Ken Schneider wrote:
Why would there be a need to open the port on the -client-? You only need to open the port on the firewall if you are acting as a server with other computers needing to connect to you.
Because it doesn't work. Try.
Then there must be a problem with the firewall.... I've never had to open ports for NTP and no routers do either that I am aware of.
Well not according to this: <http://ntp.isc.org/bin/view/Support/TroubleshootingNTP> "If you're going to run ntpd, you need to fix your network/firewall/NAT so that ntpd can have full unrestricted access to UDP port 123 in both directions." Not beeing entirely sure I believe the keyword here is UDP: http://en.wikipedia.org/wiki/Udp -- Bjørge Solli "Computers are like airconditioners, they don't work properly when you open windows..."(ukjent)
On Monday 28 November 2005 05:48 pm, Bjørge Solli wrote:
Then there must be a problem with the firewall.... I've never had to open ports for NTP and no routers do either that I am aware of.
Well not according to this: <http://ntp.isc.org/bin/view/Support/TroubleshootingNTP>
Suture self..... I can find no reference to port 123 in my router setup nor in the shorewall setup I used to run. Yet ntp is working fine.
On Tuesday 29 November 2005 00:01, Bruce Marshall wrote:
On Monday 28 November 2005 05:48 pm, Bjørge Solli wrote:
Then there must be a problem with the firewall.... I've never had to open ports for NTP and no routers do either that I am aware of.
Well not according to this: <http://ntp.isc.org/bin/view/Support/TroubleshootingNTP>
Suture self..... I can find no reference to port 123 in my router setup nor in the shorewall setup I used to run.
Yet ntp is working fine.
I am not trying to explain why it worked with our setup, I just wanted to point out why it did not work for me and suggested that could be the problem here as well. I do not know enough about your setup to try to explain why you managed without opening your router/fw. -- Bjørge Solli "Computers are like airconditioners, they don't work properly when you open windows..."(ukjent)
* Bruce Marshall <bmarsh@bmarsh.com> [11-28-05 18:04]:
Suture self..... I can find no reference to port 123 in my router setup nor in the shorewall setup I used to run.
Yet ntp is working fine.
I do not have 123 open for anything in my router, either, and have no problem with ntp. I do have 123 udp open both ways in the firewall, though. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2005-11-28 at 18:12 -0500, Patrick Shanahan wrote:
I do not have 123 open for anything in my router, either, and have no problem with ntp. I do have 123 udp open both ways in the firewall, though.
ntp uses udp, it doesn't care if tcp 123 is closed. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDi5fstTMYHG2NR9URAvqXAJ0XkXJ95Df6JcKaw3qWqjMPvjERoQCfYl9A EEWA3Ag/jLghKfmwAgfjgh8= =V6y1 -----END PGP SIGNATURE-----
On Mon, 2005-11-28 at 18:01 -0500, Bruce Marshall wrote:
On Monday 28 November 2005 05:48 pm, Bjørge Solli wrote:
Then there must be a problem with the firewall.... I've never had to open ports for NTP and no routers do either that I am aware of.
Well not according to this: <http://ntp.isc.org/bin/view/Support/TroubleshootingNTP>
Suture self..... I can find no reference to port 123 in my router setup nor in the shorewall setup I used to run.
Yet ntp is working fine.
How do you test it to make sure it's properly connected? I opened a shell (system has been rebooted between the last time and now) and linux:/home/Mike # /etc/init.d/ntp status Checking for network time protocol daemon (NTPD): running Can I assume that this means everything is working all right? This is todays entry from /var/log/ntp:
On Mon, 2005-11-28 at 18:01 -0500, Bruce Marshall wrote:
On Monday 28 November 2005 05:48 pm, Bjørge Solli wrote:
Then there must be a problem with the firewall.... I've never had to open ports for NTP and no routers do either that I am aware of.
Well not according to this: <http://ntp.isc.org/bin/view/Support/TroubleshootingNTP>
Suture self..... I can find no reference to port 123 in my router setup nor in the shorewall setup I used to run.
Yet ntp is working fine.
How do you test it to make sure it's properly connected? I opened a shell (system has been rebooted between the last time and now) and linux:/home/Mike # /etc/init.d/ntp status Checking for network time protocol daemon (NTPD): running Can I assume that this means everything is working all right? This is today's entry from /var/log/ntp: 28 Nov 00:46:11 ntpd[4865]: ntpd exiting on signal 15 28 Nov 07:19:56 ntpd[4884]: synchronized to LOCAL(0), stratum 10 28 Nov 07:19:56 ntpd[4884]: kernel time sync disabled 0041 28 Nov 07:21:00 ntpd[4884]: kernel time sync enabled 0001 28 Nov 07:22:06 ntpd[4884]: synchronized to 199.212.17.20, stratum 2 28 Nov 11:46:43 ntpd[4884]: time reset -0.303835 s 28 Nov 11:51:03 ntpd[4884]: synchronized to LOCAL(0), stratum 10 28 Nov 11:52:07 ntpd[4884]: synchronized to 199.212.17.20, stratum 2 28 Nov 12:32:51 ntpd[4884]: time reset +0.251123 s 28 Nov 12:37:07 ntpd[4884]: synchronized to LOCAL(0), stratum 10 28 Nov 12:38:13 ntpd[4884]: synchronized to 199.212.17.20, stratum 2 Mike
On Mon, 28 Nov 2005, Mike McMullin wrote:
On Mon, 2005-11-28 at 18:01 -0500, Bruce Marshall wrote:
On Monday 28 November 2005 05:48 pm, Bj�rge Solli wrote:
Then there must be a problem with the firewall.... I've never had to open ports for NTP and no routers do either that I am aware of.
Well not according to this: <http://ntp.isc.org/bin/view/Support/TroubleshootingNTP>
Suture self..... I can find no reference to port 123 in my router setup nor in the shorewall setup I used to run.
Yet ntp is working fine.
How do you test it to make sure it's properly connected? I opened a shell (system has been rebooted between the last time and now) and
linux:/home/Mike # /etc/init.d/ntp status Checking for network time protocol daemon (NTPD): running
Can I assume that this means everything is working all right? This is today's entry from /var/log/ntp:
28 Nov 00:46:11 ntpd[4865]: ntpd exiting on signal 15 28 Nov 07:19:56 ntpd[4884]: synchronized to LOCAL(0), stratum 10 28 Nov 07:19:56 ntpd[4884]: kernel time sync disabled 0041 28 Nov 07:21:00 ntpd[4884]: kernel time sync enabled 0001 28 Nov 07:22:06 ntpd[4884]: synchronized to 199.212.17.20, stratum 2
That's good news.
On Monday 28 November 2005 06:15 pm, Mike McMullin wrote:
How do you test it to make sure it's properly connected? I opened a shell (system has been rebooted between the last time and now) and
linux:/home/Mike # /etc/init.d/ntp status Checking for network time protocol daemon (NTPD): running
I usually look for barf messages in the log files... but here's the response to your commands: linux1:/logger # /etc/init.d/ntp status Checking for network time protocol daemon (NTPD): running I don't think that really guarantees that it is connected to anything... it could be just trying.
Mike McMullin wrote:
On Mon, 2005-11-28 at 18:01 -0500, Bruce Marshall wrote:
On Monday 28 November 2005 05:48 pm, Bjørge Solli wrote:
Then there must be a problem with the firewall.... I've never had to open ports for NTP and no routers do either that I am aware of.
Well not according to this: <http://ntp.isc.org/bin/view/Support/TroubleshootingNTP>
Suture self..... I can find no reference to port 123 in my router setup nor in the shorewall setup I used to run.
Yet ntp is working fine.
How do you test it to make sure it's properly connected?
You have noticed the syslog messages already. In general, you can check for the state of your NTP setup with the command ntpq -c pe It tells you about all time sources, which one is used currently, and if you're synchronized. If you have a server with an asterisk in front, you're synchronized to that server. If it has a plus in front, this is a potential source of synchronization. E.g., my company time server has the output remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) LOCAL(0) 10 l - 64 377 0.000 0.000 0.008 *ntp2.ptb.de .PTB. 1 u 887 1024 377 44.424 0.697 0.826 +rustime01.rus.u .DCFp. 1 u 968 1024 377 38.228 -2.858 0.927 +hora.cs.tu-berl .PPS. 1 u 3 1024 377 48.561 -3.353 1.365 This means we're synchronized to PTB, and if that connection gets lost, rustime01 and hora could take over. (All three servers are stratum 1 servers and give definitive times. PTB is the reference time source for Germany.) The when column is a counter that is increased until it reaches the poll number, then the next ntp request is sent. The reach column are the octal representation of 8 bits that tell when we did reach the server in the past. This is a shift register -- if it's 377, that's best, all past requests were successful. delay, offset, and jitter (all are in milliseconds) show the difference of my time server to the reference servers. More info: http://www.meinberg.de/download/docs/other/ntp_adv.txt Concerning server selection, please read http://ntp.isc.org/bin/view/Servers/NTPPoolServers. Another tip: There is a nice Nagios plugin that checks that the time server is up and running correctly; one gets an email if it gets non-functional. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany
On Mon, 2005-11-28 at 15:00 -0500, Ken Schneider wrote:
On Sun, 2005-11-27 at 21:48 -0500, Mike McMullin wrote:
On Sun, 2005-11-27 at 13:26 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2005-11-27 at 04:01 -0500, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server.
Did you remember to open the appropriate port in the firewall?
FW_SERVICES_EXT_UDP="ntp"
I haven't done much with the Firewall at all, so I'm not sure where to make that change. Could you help me on that one?
Why would there be a need to open the port on the -client-? You only need to open the port on the firewall if you are acting as a server with other computers needing to connect to you.
Noted. <sigh> Now I still need to figure out why YaST messed up when it connected on using CLI.
On Tuesday 29 November 2005 00:02, Mike McMullin wrote:
On Mon, 2005-11-28 at 15:00 -0500, Ken Schneider wrote:
On Sun, 2005-11-27 at 21:48 -0500, Mike McMullin wrote:
On Sun, 2005-11-27 at 13:26 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2005-11-27 at 04:01 -0500, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server.
Did you remember to open the appropriate port in the firewall?
FW_SERVICES_EXT_UDP="ntp"
I haven't done much with the Firewall at all, so I'm not sure where to make that change. Could you help me on that one?
Why would there be a need to open the port on the -client-? You only need to open the port on the firewall if you are acting as a server with other computers needing to connect to you.
Noted. <sigh> Now I still need to figure out why YaST messed up when it connected on using CLI.
Maybe a deamon was already running? You cannot have two instances of ntpd/xntpd/ntpdate running at the same time. -- Bjørge Solli "Computers are like airconditioners, they don't work properly when you open windows..."(ukjent)
On Tue, 2005-11-29 at 00:12 +0100, Bjørge Solli wrote:
On Tuesday 29 November 2005 00:02, Mike McMullin wrote:
On Mon, 2005-11-28 at 15:00 -0500, Ken Schneider wrote:
On Sun, 2005-11-27 at 21:48 -0500, Mike McMullin wrote:
On Sun, 2005-11-27 at 13:26 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2005-11-27 at 04:01 -0500, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server.
Did you remember to open the appropriate port in the firewall?
FW_SERVICES_EXT_UDP="ntp"
I haven't done much with the Firewall at all, so I'm not sure where to make that change. Could you help me on that one?
Why would there be a need to open the port on the -client-? You only need to open the port on the firewall if you are acting as a server with other computers needing to connect to you.
Noted. <sigh> Now I still need to figure out why YaST messed up when it connected on using CLI.
Maybe a deamon was already running? You cannot have two instances of ntpd/xntpd/ntpdate running at the same time.
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. Mike
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
On Mon, 2005-11-28 at 20:01 -0500, Carl Hartung wrote:
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.
This has got to be the explanation of what happened. When I checked it from the CLI the system had been rebooted, this would have put it in a state similar to yours, fire-wall untouched, but ntp running at next boot. I have a 9,3 and a 9.1 system that I want to set up for ntp, and I'll certainly go this route and save myself the headache. BTW who do we nag for feature requests in YaST, as this seems to be another fix to want. Mike
On Mon, 28 Nov 2005, Mike McMullin wrote:
On Mon, 2005-11-28 at 15:00 -0500, Ken Schneider wrote:
On Sun, 2005-11-27 at 21:48 -0500, Mike McMullin wrote:
On Sun, 2005-11-27 at 13:26 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2005-11-27 at 04:01 -0500, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server.
Did you remember to open the appropriate port in the firewall?
FW_SERVICES_EXT_UDP="ntp"
I haven't done much with the Firewall at all, so I'm not sure where to make that change. Could you help me on that one?
Why would there be a need to open the port on the -client-? You only need to open the port on the firewall if you are acting as a server with other computers needing to connect to you.
Noted. <sigh> Now I still need to figure out why YaST messed up when it connected on using CLI.
The router/firewall must permit outgoing traffic to the ntp UDP port. It's likely a default on some routers, blindingly obvious on others that this is a Good Thing. Some may coordinate with an external time source and run a local server: I set up my Linux firewalls that way. I recommend the use of tcpdump (or ethereal) to diagnose your difficulty.
On Sunday 27 November 2005 01:01 am, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server. Addresses are provided by YaST's NTP Client module. Has anyone success in setting up 10.0 with a N.A. time server?
works fine here. I did have an issue with one server, but it works on others. Remember the command is different than it was in 9.3 and previous. yoda:/home/kai # /etc/init.d/ntp start ..dead Try to get initial date and time via NTP from clock.sjc.he.net done Starting network time protocol daemon (NTPD) done -- kai www.perfectreign.com linux - genuine windows replacement part
On Sun, 2005-11-27 at 13:37 -0800, Kai Ponte wrote:
On Sunday 27 November 2005 01:01 am, Mike McMullin wrote:
I've been trying to set up my 10.0 machine as an ntp client. The software is installed but when it tries to validate a server (I've tried several in the Canada and the U.S) it tells me it cannot reach the server. Addresses are provided by YaST's NTP Client module. Has anyone success in setting up 10.0 with a N.A. time server?
works fine here. I did have an issue with one server, but it works on others. Remember the command is different than it was in 9.3 and previous.
yoda:/home/kai # /etc/init.d/ntp start ..dead Try to get initial date and time via NTP from clock.sjc.he.net done Starting network time protocol daemon (NTPD) done
It took a bit of fussing, but the command line worked. here's the info linux:/home/Mike # /etc/init.d/ntp start Starting network time protocol daemon (NTPD) done linux:/home/Mike # /etc/init.d/ntp status \Checking for network time protocol daemon (NTPD): running linux:/home/Mike # /etc/init.d/ntp ntptimeset Can't set time while ntpd is running failed linux:/home/Mike # /etc/init.d/ntp stop Shutting down network time protocol daemon (NTPD) done linux:/home/Mike # /etc/init.d/ntp ntptimeset Try to get initial date and time via NTP from ntp2.cmc.ec.gc.ca done linux:/home/Mike # /etc/init.d/ntp status Checking for network time protocol daemon (NTPD): unused linux:/home/Mike # /etc/init.d/ntp start Try to get initial date and time via NTP from ntp2.cmc.ec.gc.ca done Starting network time protocol daemon (NTPD) done I've got a question about NTP and the firewall (I haven't made any firewall changes), but I'm wondering why it connected to the server from CLI and not in YaST. Mike
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2005-11-27 at 21:59 -0500, Mike McMullin wrote:
I've got a question about NTP and the firewall (I haven't made any firewall changes), but I'm wondering why it connected to the server from CLI and not in YaST.
Ghosts! :-p - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDiwAJtTMYHG2NR9URArvJAKCWweuc/FwQY1q2bymm/oYTwL/VHACaA8TR qYQql/iJ9Rw5AtgECh+aZyE= =uJwN -----END PGP SIGNATURE-----
participants (10)
-
Bjørge Solli -
Bruce Marshall -
Carl Hartung -
Carlos E. R. -
Joachim Schrod -
John Summerfield -
Kai Ponte -
Ken Schneider -
Mike McMullin -
Patrick Shanahan