Re: Time/Date via Gnome clock app (sid)

2007-04-17 Thread Sven Arvidsson
On Mon, 2007-04-16 at 00:05 +0200, Andrea S. Gozzi wrote: > I've set up my primary sid desktop to update time with NTP via the Gnome > clock application. > Now it seems that the NTP server has gone offline and the displayed time > has a -5min difference with the real one. I wanted to use the server

Re: Time/Date via Gnome clock app (sid)

2007-04-15 Thread Ron Johnson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/15/07 17:05, Andrea S. Gozzi wrote: > Hi. > I've set up my primary sid desktop to update time with NTP via the Gnome > clock application. > Now it seems that the NTP server has gone offline and the displayed time > has a -5min difference with the

RE: TIME, DATE and CRON... trap for the unwary

2001-07-22 Thread Ian Perry
Yes, restarting crond would also work I have been working with windoze too long rebooting all the time is rubbing off. > -Original Message- > From: Walt Mankowski [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 21, 2001 8:13 AM > To: 'Debian Users' > Su

Re: TIME, DATE and CRON... trap for the unwary

2001-07-20 Thread Walt Mankowski
On Fri, Jul 20, 2001 at 10:15:00AM +1000, Ian Perry wrote: > Hi All, > > Just came across a point about Time and Date and CRON which could cause a > problem for those who are unaware. > > If you have CRON running and you set back the Date or Time backwards, CRON > will not run until at least the

Re: TIME, DATE and CRON... trap for the unwary

2001-07-20 Thread John Galt
On Fri, 20 Jul 2001, Ian Perry wrote: >Hi All, > >Just came across a point about Time and Date and CRON which could cause a >problem for those who are unaware. > >If you have CRON running and you set back the Date or Time backwards, CRON >will not run until at least the old time has been reached a

Re: TIME, DATE and CRON... trap for the unwary

2001-07-19 Thread David Z Maze
Ian Perry <[EMAIL PROTECTED]> writes: IP> Hi All, IP> Just came across a point about Time and Date and CRON which could cause a IP> problem for those who are unaware. IP> IP> If you have CRON running and you set back the Date or Time backwards, CRON IP> will not run until at least the old time has

Re: time/date problems

2000-02-12 Thread Ethan Benson
On Sat, Feb 12, 2000 at 11:42:26AM +, Ed Cogburn wrote: > > > I'll look at this when I have some time, but when my machine shuts > down I see a message saying "hardware clock being updated" or > something like that. This behavior may be part of the ntpdate > package, I didn't consider

Re: time/date problems

2000-02-12 Thread Ed Cogburn
David Wright wrote: > > Quoting Ed Cogburn ([EMAIL PROTECTED]): > > > > This isn't exactly true. You can keep your hardware clock on local, > > and you can tell Linux to use local time (keeping it from messing > > around). Linux does not set my hardware clock to GMT at shutdown, it > > set

Re: time/date problems

2000-02-11 Thread Brad
On Fri, Feb 11, 2000 at 02:32:16AM -0900, Ethan Benson wrote: > > I don't think Linux will adjust for Daylight savings unless the > hardware clock is in GMT, otherwise it would just end up being a race > condition with the broken OS also installed (why else would you have > your HW clock set to lo

Re: time/date problems

2000-02-11 Thread David Wright
Quoting Ed Cogburn ([EMAIL PROTECTED]): > > This isn't exactly true. You can keep your hardware clock on local, > and you can tell Linux to use local time (keeping it from messing > around). Linux does not set my hardware clock to GMT at shutdown, it > sets it with local time, which is wha

Re: time/date problems

2000-02-11 Thread Ethan Benson
On Fri, Feb 11, 2000 at 10:52:47AM +, Ed Cogburn wrote: I wrote: > > if you must have correct time in windows you will have to reconfigure > > linux to keep time in local time instead of GMT. [...] > ^^ > > This isn't

Re: time/date problems

2000-02-11 Thread Ed Cogburn
Ethan Benson wrote: > > On Fri, Feb 11, 2000 at 09:23:36AM +1300, [EMAIL PROTECTED] wrote: > > Hi > > > > i am running slink 2.1 with kernel 2.0.36 on a Dell Power Edge 2100 and i > > am having problems with the time. Basically what happens is that once i > > set up the correct date/time in BIOS.

London not = GMT/UTC (was Re: time/date problems)

2000-02-11 Thread David Wright
Quoting Ethan Benson ([EMAIL PROTECTED]): > > if you must have correct time in windows you will have to reconfigure > linux to keep time in local time instead of GMT. personally i just > set the broken OS's (in my case MacOS) timezone to London, England > (GMT) so it won't corrupt the hardware cl

Re: time/date problems

2000-02-11 Thread Ethan Benson
On Fri, Feb 11, 2000 at 09:23:36AM +1300, [EMAIL PROTECTED] wrote: > Hi > > i am running slink 2.1 with kernel 2.0.36 on a Dell Power Edge 2100 and i > am having problems with the time. Basically what happens is that once i > set up the correct date/time in BIOS...when i load up linux the time &

Re: time$date

1999-01-30 Thread Chuck Stickelman
[EMAIL PROTECTED] wrote: G'day to all. Howdy! i have a problem with my system's time and date i'm using debian 2.0.36and my time is about 12hrs ahead of what it should be! Just a guess, but how many hours away from GMT are you?  My guess is that your system is not consistantly using GMT vs. l

Re: time$date

1999-01-30 Thread Bob Nielsen
On Sun, 31 Jan 1999 [EMAIL PROTECTED] wrote: > > G'day to all. i have a problem with my system's time and date i'm > using debian 2.0.36and my time is about 12hrs ahead of what it should > be! doesanyone know how to reset the time and date as star office and > cron jobs ate all out of sync t