I ran into the same problem as the daylight savings time kicked in Sunday night for us... but... >The simple solution is step 12) below. However you should read the >message below and follow the part that applies to you. > >All timezone changes are made using timeconfig. > >I) > >If you are _not_ already using glibc-2.0.7-5 from the Red Hat updates >directory: > >1) Make sure your Hardware clock is set to GMT. >2) Make sure the "Hardware clock set to GMT" option is checked. >3) Ensure that the Europe/Amsterdam (or CET) timezone is selected >4) Upgrade to glibc-2.0.7-5 from the Red Hat updates directory >5) Try Bru >6) If it doesn't work try swapping the timezone to CET (or >Europe/Amsterdam) >7) Try Bru >8) If it doesn't work goto step 12) in part II > >II) > >If you are already using glibc-2.0.7-5 from the Red Hat updates >directory _or_ if you don't want to change your glibc: > >9) Make sure your Hardware clock is set to GMT. >10) Make sure the "Hardware clock set to GMT" option is checked. >11) Do steps 3) and 5) and if necessary steps 6) and 7) in part I. >12) If it still doesn't work change your timezone to Etc/GMT+2 >(assuming that you are now 2hrs ahead of GMT) Tried all of the above... upgraded to glibc-2.0.7-5 (do I need to rebuild BRU afterwards?). Check my clock settings: [root@beast RPMS]# date Mon Apr 6 15:46:23 PDT 1998 [root@beast RPMS]# date -u Mon Apr 6 22:46:27 UTC 1998 [root@beast RPMS]# clock -r Mon Apr 6 22:46:30 1998 -0.429371 seconds [root@beast RPMS]# clock -ru Mon Apr 6 15:46:33 1998 -0.731667 seconds Seems fine... my timezone was set to US/PST, bru didn't work with that so I changed it to: PST8PDT and yes, the hardware clock is set to GMT... x Format machine time is stored in: x x [*] Hardware clock set to GMT x Still no go.... I still don't see why the time change should give this kind of error from BRU in the first place... :-( - paul -------------------Kudosnet Communication Services-------------------- [EMAIL PROTECTED] www.kudosnet.com For value added web hosting and internet commerce sites http://kudosnet.com/services/ -------------879 View Rd. Qualicum Beach, Canada V9K 1N3-------------- -- PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES! http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
Re: bru: [E134] internal error 100 - .....
Paul Evad - Kudosnet Communications Mon, 6 Apr 1998 18:58:04 -0400
- Re: Just can't connect (was: send... Paul Fontenot
- Re: Just can't connect (was: sendmail ... Joe_Ferguson
- Re: Just can't connect (was: sendmail ... Joe_Ferguson
- Re: Just can't connect (was: send... Paul Fontenot
- Re: Just can't connect (was: sendmail ... Dan Cyr
- Re: Just can't connect (was: sendmail ... Joe_Ferguson
- Re: Just can't connect (was: sendmail ... Win Htin
- bru: [E134] internal error 100 - ... Hans Sandsdalen
- Re: bru: [E134] internal erro... Eze Ogwuma
- Re: bru: [E134] internal ... Hans Sandsdalen
- Re: bru: [E134] internal ... Paul Evad - Kudosnet Communications
- Re: bru: [E134] inter... Eze Ogwuma
- Re: bru: [E134] ... Ray Curtis
- Re: bru: [E134] inter... Phil Risby
- Re: Just can't connect (was: sendmail ... Joe_Ferguson
- Re: Just can't connect (was: sendmail ... Dan Cyr
- Re: Just can't connect (was: sendmail ... Raymond Fung
- Re: Just can't connect (was: send... Kristoffer Stovring
- Re: Just can't connect (was: sendmail ... Joe_Ferguson
- Re: Just can't connect (was: sendmail ... Joe_Ferguson