dist: RedHat Linux 5.1
kernel: 2.0.34
clib: glibc-2.0.7-13
compiler: pgcc-1.0.3a
diald: 0.16.5 & diald-config-1.2.1
In addition to the "Unable to open options file" error I just
reported to the list, I am having yet another problem with diald.
When ever diald logs to the accounting-log /var/log/diald.log, I
get the following:
Mon Jul 13 19:04:32 1998 /etc/localtime: Calling site 0.0.0.0.
Mon Jul 13 19:05:08 1998 /etc/localtime: Connected to site 0.0.0.0.
Mon Jul 13 19:11:48 1998 /etc/localtime: Disconnected. Call duration 400 seconds.
IP transmitted 9984 bytes and received 32731 bytes.
It is logging /etc/localtime instead of EDT which it used to log.
Additionally, the time stamp is 4 hours ahead to the actual time.
Now I do have my BIOS hardware clock set to UTC, but it has
always been that way and never caused problems with anything
before. If I remove /etc/localtime and run date, I get the same
thing. /etc/localtime in place of EDT, and the time is in UTC.
Otherwise date produces EDT and the correct time. I guessing
that this is related to glibc, but since I've been running glibc
since RedHat 5.0 came out.
Any help would be greatly appreciated.
-- "J Kinsley" <jkinsley at BeYoND-THe-iLLuSioN dot CoM> *********************************************************************** ** On a planet that increasingly resembles one huge Maximum *** ** Security Prison, the only intelligent [and logical] choice is to *** ** plan a Jail Break -- Robert Anton Wilson (Cosmic Trigger II) *** *********************************************************************** [IX] >> (([I]+[II])+>([VI]+[XIV]+[XI])+>([V]+[XXI])) => (I=II+V) >>> IX
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html