Report information
The Basics
Id:
30780
Status:
open
Priority:
Low/Low
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
(no value)
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
(no value)
Severity:
S3 Low
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
feature

Dates
Created:Mon, 27 Aug 2012 08:39:48 -0400
Updated:Fri, 07 Jul 2017 21:17:17 -0400
Closed:Not set



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: 2 time-zone related suggestions
Date: Mon, 27 Aug 2012 14:39:35 +0200
To: dhcp-suggest@isc.org
From: Jiri Popelka <jpopelka@redhat.com>
Hi, I have 2 suggestions regarding time&date format printing and parsing. First, as you can see in [1] it is not easy to discover what time zone the time&date record in leases file are. One needs to read dhclient.conf(5) to know that in 'default' format they are in UTC. But the time zone indication would be useful also in 'local' format. See attached timezone.patch Second, I think the common/parse.c::parse_date_core() is a little outdated, because it is able to parse a time zone offset, but I can't find an origin of this tz offset, i.e. common/print.c::print_time() doesn't create such a thing. See tzoff.patch [1] http://bugzilla.redhat.com/show_bug.cgi?id=851636 With regards, Jiri Popelka Red Hat, inc.

Message body is not shown because sender requested not to inline it.

Message body is not shown because sender requested not to inline it.