Bug 75715 - Timestamps on jobs are wrong
Summary: Timestamps on jobs are wrong
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: cups   
(Show other bugs)
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-11 13:53 UTC by Need Real Name
Modified: 2007-04-18 16:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-12-09 16:43:03 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Need Real Name 2002-10-11 13:53:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; AT&T CSM6.0; 
T312461)

Description of problem:
The timestamps on jobs printed with cups are wrong.  In my case the time is 5 
hours later than it should be.  Is cups perhaps showing timestamps in UTC?

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Go to cups printer admin
2. Print a test page
3. Look at the timestamp in the active or completed jobs
	

Actual Results:  Timestamps are 5 hours ahead of actual time job is/was printed.

Expected Results:  Timestamp should reflect the time the job was printed in the 
server timezone.

Additional info:

   HPNAT-67  Test Page    15k  cancelled at
   Fri Oct 11 13:44:40 2002  Restart Job

   Show Active Jobs
     _________________________________________________________________
[####]# date
Fri Oct 11 08:49:57 CDT 2002
[####]# cat /etc/sysconfig/c
clock    console
[####]# cat /etc/sysconfig/clock
ZONE="America/Chicago"
UTC=false
ARC=false

Comment 1 Tim Waugh 2002-10-11 14:03:56 UTC
Yes, that's UTC.

Comment 2 Tim Waugh 2002-10-11 14:26:30 UTC
Confusingly, 'lpstat' shows the local time zone, but also omits time zone 
information from its output.

Comment 3 Tim Waugh 2004-12-09 16:43:03 UTC
Seems to be intentional.


Note You need to log in before you can comment on or make changes to this bug.