> I'll look at getting the man pages fixed.
I've filed https://bugzilla.kernel.org/show_bug.cgi?id=218711 against the
strftime man page.
For localtime(), it may be sufficient that the man page indicates that
localtime() behaves as if tzset() were called, and that the tzset man page
indicates
> Very little, if anything, of strftime() needs to handle TZ, because it's
> handed a const struct tm *, generated either by a call to localtime() or
> gmtime() If generated by a call to localtime(), localtime() has already done
> all the work of converting a time_t to local time, meaning that
> tcpdump has no special handling of TZ, it just calls strftime() which handles
> TZ as described in strftime(3).
Very little, if anything, of strftime() needs to handle TZ, because it's handed
a const struct tm *, generated either by a call to localtime() or gmtime() If
generated by a call
* Romain Francoise [2024-03-17 19:52]:
>
> tcpdump has no special handling of TZ, it just calls strftime() which
> handles TZ as described in strftime(3).
Thanks for the quick feedback.
That’s a bit tricky one then. Users of tcpdump wouldn’t generally know
that strftime() is in use and thus
tcpdump has no special handling of TZ, it just calls strftime() which
handles TZ as described in strftime(3).
--
Romain Francoise
https://people.debian.org/~rfrancoise/
Package: tcpdump
Version: 4.99.0-2+deb11u1
Severity: minor
Tags: upstream
X-Debbugs-Cc: debbug.tcpd...@sideload.33mail.com
Normally by convention useful environmental variables are documented
in an ENVIRONMENT section of the man page. There is no coverage of any
env vars in the man page. I was
6 matches
Mail list logo
