Bug 189878

Summary: newsyslog(8) confused by some timezones (apparently)
Product: Base System Reporter: Kurt Lidl <lidl>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Open ---    
Severity: Affects Only Me    
Priority: Normal    
Version: 9.1-RELEASE   
Hardware: Any   
OS: Any   

Description Kurt Lidl freebsd_committer freebsd_triage 2014-05-17 01:50:00 UTC 
The time parsing routines in use by the newsyslog program are apparently not terribly robust.
On many timezones, they fail to parse the "when" field of the newsyslog.conf if it
contains a valid with a leading asterisk.  e.g. "@T00" - both given as an example in
the manpage, as well as in the distributed /etc/newsyslog.conf file.

The behavior is reproducable on 9.1-RELEASE, stable/9, stable/10 and "head" as of
today (May 16, 2014).

How-To-Repeat: TZ=UTC newsyslog -s -C -n -r

Notice that output is generated.

TZ=EST5DT newsyslog -s -C -n -r

Notice that no output is generated.

Under a system running stable/9.2-ish, I get output like this in the failing case:
# TZ=EST5EDT newsyslog -s -C -n -r
newsyslog: malformed 'at' value:
/var/log/maillog                        640  7     *    @T00  C

(it dies at whatever the first line with an "@...." in the when field.)
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:16 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped