[SLE] ntp client -- warning from yast
using SUSE10, when I went into yast to enable the ntp client, I am warned about setting it to execute "on boot". The warning says: "Warning! If you do not have a permanent internet connection, starting the NTP daemon can take a very long time, and the daemon might not run properly" Huh? So, if I have a laptop, that does not at all times have an inet connection, basically I should not use the NTP client? Is there any good way to, once an inet connection IS established, sync time to an NTP server? Yast seems to only give "never" and "on boot" as ntp sync options. If there is a command I can execute from a shell, that would be fine. Peter -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Tuesday 25 July 2006 09:43, Peter Van Lone wrote:
using SUSE10, when I went into yast to enable the ntp client, I am warned about setting it to execute "on boot". The warning says:
"Warning! If you do not have a permanent internet connection, starting the NTP daemon can take a very long time, and the daemon might not run properly"
Huh?
When you boot and start up ntp, it will try to go out and set the time and if you don't have a connection, it is going to hang there for a timeout. Not good. A much better way to set the time on a laptop would be to have a cron job that uses ntpdate. Twice a day should be enough.
So, if I have a laptop, that does not at all times have an inet connection, basically I should not use the NTP client? Is there any good way to, once an inet connection IS established, sync time to an NTP server?
Yast seems to only give "never" and "on boot" as ntp sync options. If there is a command I can execute from a shell, that would be fine.
Peter
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Bruce Marshall wrote:
On Tuesday 25 July 2006 09:43, Peter Van Lone wrote:
using SUSE10, when I went into yast to enable the ntp client, I am warned about setting it to execute "on boot". The warning says:
"Warning! If you do not have a permanent internet connection, starting the NTP daemon can take a very long time, and the daemon might not run properly"
Huh?
When you boot and start up ntp, it will try to go out and set the time and if you don't have a connection, it is going to hang there for a timeout.
Not good.
I have watched the boot process, with ntpd enabled and no network connection. The timeout isn't very long, perhaps a few seconds. It doesn't have much effect on booting. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Tuesday 25 July 2006 9:43 am, Peter Van Lone wrote:
using SUSE10, when I went into yast to enable the ntp client, I am warned about setting it to execute "on boot". The warning says:
"Warning! If you do not have a permanent internet connection, starting the NTP daemon can take a very long time, and the daemon might not run properly"
Huh?
So, if I have a laptop, that does not at all times have an inet connection, basically I should not use the NTP client? Is there any good way to, once an inet connection IS established, sync time to an NTP server?
Yast seems to only give "never" and "on boot" as ntp sync options. If there is a command I can execute from a shell, that would be fine. One solution is to use profiles. (SCPM). On my laptop, I have a number of different places where I use it whith different networks, and some networks have different time servers: work - wired, time server in intranet. home - wired and wireless MIT Open Wireless for places where I might alternatively take the laptop.
In my case, the profile disables the built-in NIC when using wireless and vice-versa when wired. I also include /etc/sysconfig/proxy. You can set up the initial profiles via YaST/System/Profile Manager, and select the appropriate profile using F3 when booting up (SuSE 10.x). -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
/etc/init.d/ntp is where it is started. You could manually bring it up or write a front end to know if the network was up and then run it I suppose. Peter Van Lone wrote:
using SUSE10, when I went into yast to enable the ntp client, I am warned about setting it to execute "on boot". The warning says:
"Warning! If you do not have a permanent internet connection, starting the NTP daemon can take a very long time, and the daemon might not run properly"
Huh?
So, if I have a laptop, that does not at all times have an inet connection, basically I should not use the NTP client? Is there any good way to, once an inet connection IS established, sync time to an NTP server?
Yast seems to only give "never" and "on boot" as ntp sync options. If there is a command I can execute from a shell, that would be fine.
Peter
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Tuesday 25 July 2006 10:03 am, Robert Lewis wrote: > /etc/init.d/ntp is where it is started. > You could manually bring it up or write a front end to > know if the network was up and then run it I suppose. Actually, on bootup, as Bruce mentioned, ntpdate(1) is attempted, and this is the guy who takes the time. There are a number of workable solutions: 1. The one I proposed. A bit complex. 2. The one Bruce Proposed. Requires a simple crontab entry. 3. Tell ntp not to start ntpdate. This can be done in Yast/System/Sysconfig editor/Network/NTP/NTPD_INITIAL_NTPDATE. In this case, only the ntp daemon will run, and this will not delay startup at all, and won't cause any performance issues. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 7/25/06, Peter Van Lone <petervl@gmail.com> wrote:
using SUSE10, when I went into yast to enable the ntp client, I am warned about setting it to execute "on boot". The warning says:
"Warning! If you do not have a permanent internet connection, starting the NTP daemon can take a very long time, and the daemon might not run properly"
Huh?
So, if I have a laptop, that does not at all times have an inet connection, basically I should not use the NTP client? Is there any good way to, once an inet connection IS established, sync time to an NTP server?
Yast seems to only give "never" and "on boot" as ntp sync options. If there is a command I can execute from a shell, that would be fine.
Peter
You may as well try using /etc/sysconfig/network/if-up.d and if-down.d. Or for per interface control - ifservices-xxxx. man ifup and man ifservices for more info. Put in these directories scripts which start/stop ntpd when and interface is started/stopped. -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Peter Van Lone wrote:
using SUSE10, when I went into yast to enable the ntp client, I am warned about setting it to execute "on boot". The warning says:
"Warning! If you do not have a permanent internet connection, starting the NTP daemon can take a very long time, and the daemon might not run properly"
Huh?
So, if I have a laptop, that does not at all times have an inet connection, basically I should not use the NTP client? Is there any good way to, once an inet connection IS established, sync time to an NTP server?
Yast seems to only give "never" and "on boot" as ntp sync options. If there is a command I can execute from a shell, that would be fine.
You can always start ntpd manually or use ntpdate. However, I have it enabled to start at boot on my notebook, with no problems. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (6)
-
Bruce Marshall -
James Knott -
Jerry Feldman -
Peter Van Lone -
Robert Lewis -
Sunny