Hi,
On Tue, 11 Jul 2006 19:37:44 +0200 Per Jessen <.> wrote:
pelibali wrote:
I have a perl-script to modify the system-time of my laptop.
Using perl sounds like overkill :-) - doesn't ntpdate cover it?
Yeah sure, I load it from a perl-script, just together with hwclock ;)))
While I was connected to my university's broadband, I could run this via cron once per day. Now I have only dial-up at my home, so really can't determine whether I will be online, when this script runs.
So you run it as part of your dial-in procedure. It's been awhile since I've used dial-in, but I'm sure there a place where you can add a hook and get your system time set once the connection is up.
I think I can't simply run it like this, because we have various comps in our network and usually I'm not the one dialling in through the router's (SUSE 10.0) opened smpppd. Install ntp on the router, and configure it to start on boot. It will, of course, be unable to connect to any time servers until a dial-up connection is established, but at the same time should be able to
On 11/07/06 12:03, pelibali wrote: provide reasonable time control during times when it is not connected. Once you are satisfied ntp is operating satisfactorily as a client on the internet, configure it as a time server for your internal network, and configure ntp in client-only mode on your personal system (to start at boot, of course) to use the router as a time server. Now you don't care if the dial-up connection is already established or not. As a less attractive alternative, you can configure ntp in server-only mode on the router, and use adjtimex in the dial-up script to reset the router's system time when a connection is established. Again configure ntp in client mode on your personal system to use the router as a time server. -- 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