Problem
The timestamps for uulog(C), uucp(C), uux(C), and other uu* commands
are incorrectly marked with GMT on the receiving machine. The
sending machine's log will have a correct timestamp.In the example below, the machine "cheetah" is transferring a file to the machine "jaguar"; cheetah's logfile gets a correct timestamp but jaguar's is incorrect:
cheetah# uucp hi jaguar!/tmp
cheetah# uulog -f jaguar
uucp jaguar (6/23-15:32:12,9709,0) SUCCEEDED (call to jaguar )
uucp jaguar (6/23-15:32:14,9709,0) OK (startup TCP,e)
root jaguar jaguarN36ef (6/23-14,15:32:9709,0) REQUEST (cheetah!/tmp/hi -->
jaguar!/tmp (root))
uucp jaguar (6/23-15:32:15,9709,1) OK (conversation complete TCP,e 7)However, the uulog on jaguar looks like this, even though both machines are in the same timezone:
jaguar# uulog -f cheetah
uucp cheetah (6/23-21:32:20,4799,0) OK (startup notty)
uucp cheetah (6/23-21:32:20,4799,0) REMOTE REQUESTED (cheetah!/tmp/hi -->
jaguar!/tmp (root))
uucp cheetah (6/23-21:32:20,4799,1) OK (conversation complete notty 2)This problem should only occur on machines configured to use UUCP over TCP.
Cause
The local timezone is not recorded correctly, even if /etc/TIMEZONE
has a correct setting. The type of UUCP protocol used ("e" protocol
or "g" protocol) has no affect on the timestamp logging. Solution
This has been reported to SCO Engineering.