On Sat 06 Jan 2024 at 02:57:53 (-0600), Nate Bargmann wrote:
> * On 2024 06 Jan 01:00 -0600, Max Nikulin wrote:
> > US/Eastern & Co has been moved to tzdata-legacy as well. Currently used
> > identifiers are based on cities: America/New_York.
>
> Ugghhh!
>
> I guess I'll be going to the legacy
On Sat, Jan 06, 2024 at 01:17:13PM -0600, John Hasler wrote:
> Try manpages.org .
> --
> John Hasler
> j...@sugarbit.com
> Elmwood, WI USA
>
If you're on a Debian system, this should already be installed but otherwise
apt-get install manpages
Also - manpages.debian.org gives you a searchable
On 1/6/24 12:07, Max Nikulin wrote:
On 06/01/2024 18:40, gene heskett wrote:
Put all system clocks on UTC, and then /etc/timezone is the actual
string specifying the local offset. No doubt some user confusion, but
overall a lot simpler.
I still do not see any connection with splitting a part
Try manpages.org .
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 1/6/24 09:25, John Hasler wrote:
The documentation for Chrony is:
chrony.conf (5) - chronyd configuration file
chronyc (1) - command-line interface for chrony daemon
chronyd (8) - chrony daemon
Also see /usr/share/doc/chrony .
Don't use "pool" to sync to a single
On 06/01/2024 18:40, gene heskett wrote:
Put all system clocks on UTC, and then /etc/timezone is the actual
string specifying the local offset. No doubt some user confusion, but
overall a lot simpler.
I still do not see any connection with splitting a part of files and
links into another
On Sat, Jan 06, 2024 at 02:57:53AM -0600, Nate Bargmann wrote:
> I really don't get the fascination with some city hundreds of miles
> distant defining the time zone. Why Chicago for US/Central? There are
> any number of cities in US/Central that could be referenced, but no,
> pick the most
The documentation for Chrony is:
chrony.conf (5) - chronyd configuration file
chronyc (1) - command-line interface for chrony daemon
chronyd (8) - chrony daemon
Also see /usr/share/doc/chrony .
Don't use "pool" to sync to a single source. Use "server".
man chrony.conf
On 1/6/24 04:15, Nate Bargmann wrote:
* On 2024 06 Jan 01:00 -0600, Max Nikulin wrote:
US/Eastern & Co has been moved to tzdata-legacy as well. Currently used
identifiers are based on cities: America/New_York.
Ugghhh!
I guess I'll be going to the legacy package then until
On 1/6/24 01:18, Max Nikulin wrote:
On 06/01/2024 12:18, gene heskett wrote:
On 1/5/24 23:29, Greg Wooledge wrote:
On Fri, Jan 05, 2024 at 09:01:29PM -0500, Charles Kroeger wrote:
tzdata (2023d-1) unstable; urgency=medium
upstream backward file) were moved to tzdata-legacy. This
* On 2024 06 Jan 01:00 -0600, Max Nikulin wrote:
> US/Eastern & Co has been moved to tzdata-legacy as well. Currently used
> identifiers are based on cities: America/New_York.
Ugghhh!
I guess I'll be going to the legacy package then until
$WHOEVER_IS_IN_CHARGE issues a decree that it too shall
On 06/01/2024 13:02, Max Nikulin wrote:
The change affects those who rely on POSIX-like EST5EDT timezones or on
obsolete ones like Europe/Kyiv (recently renamed from Europe/Kiev).
Europe/Kiev (moved to tzdata-legacy) was renamed to Europe/Kyiv. Sorry
for confusion.
US/Eastern & Co has been
On 06/01/2024 12:18, gene heskett wrote:
On 1/5/24 23:29, Greg Wooledge wrote:
On Fri, Jan 05, 2024 at 09:01:29PM -0500, Charles Kroeger wrote:
tzdata (2023d-1) unstable; urgency=medium
upstream backward file) were moved to tzdata-legacy. This includes the
What's wrong with NTP, too
13 matches
Mail list logo
