On Tue, 2 Dec 2008 17:15:08 -0500, "Kristian Kielhofner" <[EMAIL PROTECTED]> wrote: > On Mon, Dec 1, 2008 at 4:20 PM, Philip Prindeville > <[EMAIL PROTECTED]> wrote: >> I just realized that the same script /etc/init.d/zaptel that loads up >> "ztdummy" (which interferes with the "hwclock" command and setting the >> time) also starts/stops "wanrouter" for DSL or T1 or T3 users (who >> connect to the Internet via the latter)... >> >> So if you're thinking you can run "/etc/init.d/zaptel stop", synchronize >> your ntpd, write out the time to the clock via "hwclock -wu", and >> restart zaptel... well, you're in for a surprise. >> >> You can't, because the "zaptel stop" will bring down your outside >> connectivity. >> >> Oops. >> >> -Philip > > ...and "wanrouter start" should bring it back...
Which would be hard if you were in say Seattle and your router was in Boise... With the changes committed the other day, new releases will again properly do this on shutdown. The safest bet would be to reboot. Darrick ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
