Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #245031 > unrolled thread

date & X copy/paste broke on upgrading to Debian 11

Back to article view | Back to linux.debian.user

Contents

  date & X copy/paste broke on upgrading to Debian 11 José Luis González <bugs.jlg@gmail.com> - 2022-02-06 11:10 +0100
    Re: date & X copy/paste broke on upgrading to Debian 11 "Thomas Schmitt" <scdbackup@gmx.net> - 2022-02-06 11:30 +0100
      Re: date & X copy/paste broke on upgrading to Debian 11 Greg Wooledge <greg@wooledge.org> - 2022-02-06 15:20 +0100
        Re: date & X copy/paste broke on upgrading to Debian 11 José Luis González <bugs.jlg@gmail.com> - 2022-02-06 22:00 +0100
    Re: date & X copy/paste broke on upgrading to Debian 11 "Andrew M.A. Cater" <amacater@einval.com> - 2022-02-06 12:30 +0100
      Re: date & X copy/paste broke on upgrading to Debian 11 José Luis González <bugs.jlg@gmail.com> - 2022-02-06 22:00 +0100
    Re: date & X copy/paste broke on upgrading to Debian 11 Teemu Likonen <tlikonen@iki.fi> - 2022-02-06 13:10 +0100
      Re: date & X copy/paste broke on upgrading to Debian 11 Greg Wooledge <greg@wooledge.org> - 2022-02-06 15:20 +0100
        Re: date & X copy/paste broke on upgrading to Debian 11 David Wright <deblis@lionunicorn.co.uk> - 2022-02-06 18:00 +0100
          Re: date & X copy/paste broke on upgrading to Debian 11 Greg Wooledge <greg@wooledge.org> - 2022-02-06 18:20 +0100
            Re: date & X copy/paste broke on upgrading to Debian 11 Brian <ad44@cityscape.co.uk> - 2022-02-06 20:00 +0100
              Re: date & X copy/paste broke on upgrading to Debian 11 José Luis González <bugs.jlg@gmail.com> - 2022-02-06 22:00 +0100
                Re: date & X copy/paste broke on upgrading to Debian 11 Greg Wooledge <greg@wooledge.org> - 2022-02-06 22:00 +0100
                  Re: date & X copy/paste broke on upgrading to Debian 11 José Luis González <bugs.jlg@gmail.com> - 2022-02-07 00:00 +0100
                    Re: date & X copy/paste broke on upgrading to Debian 11 Greg Wooledge <greg@wooledge.org> - 2022-02-07 00:10 +0100
                      Re: date & X copy/paste broke on upgrading to Debian 11 David Wright <deblis@lionunicorn.co.uk> - 2022-02-07 03:10 +0100
                        Re: date & X copy/paste broke on upgrading to Debian 11 Greg Wooledge <greg@wooledge.org> - 2022-02-07 03:30 +0100
              Re: date & X copy/paste broke on upgrading to Debian 11 Michael Stone <mstone@debian.org> - 2022-02-07 04:10 +0100
        Re: date & X copy/paste broke on upgrading to Debian 11 Charles Curley <charlescurley@charlescurley.com> - 2022-02-06 18:00 +0100
          Re: date & X copy/paste broke on upgrading to Debian 11 Brian <ad44@cityscape.co.uk> - 2022-02-06 18:10 +0100

#245031 — date & X copy/paste broke on upgrading to Debian 11

Hi,

Upon upgrading to Debian 11 several things broke.

The two that come to my attention now are:

1. System time is one hour more than it should. Timezone (as set by
tzdata) is correct.

2. Copy and paste in X don't work anymore by selecting and clicking on
mouse button 2.

I'm running XFCE, if it is of any help.

[toc] | [next] | [standalone]

#245032

Hi,

José Luis González wrote:
> 2. Copy and paste in X don't work anymore by selecting and clicking on
> mouse button 2.

"bracketed paste", maybe ?

It was discussed on this list in the recent months.
See

  https://lists.debian.org/cgi-bin/search?P=bracketed+paste&DEFAULTOP=or&B=Gdebian-user&SORT=&HITSPERPAGE=10


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#245039

On Sun, Feb 06, 2022 at 11:25:36AM +0100, Thomas Schmitt wrote:
> Hi,
> 
> José Luis González wrote:
> > 2. Copy and paste in X don't work anymore by selecting and clicking on
> > mouse button 2.
> 
> "bracketed paste", maybe ?

Depends on where he's pasting.  Bracketed paste doesn't actually stop
middle-click pastes from working in bash in a terminal; it just makes
it look weird, and requires a confirming Enter keypress if you paste
commands with newlines in them.

José, *where* are you trying to paste, that isn't working?  At a bash
prompt?  Inside an editor running in a terminal?  Inside an editor
that is a GUI program?  Inside some other GUI program like a web
browser?

vim for example now has a default system-wide vimrc configuration that
does funky things with the mouse, and interferes with traditional
middle-click pasting.  If you're having this issue in vim, you can
work around it by doing either of these two things:

1) Have a personal ~/.vimrc file that overrides the system default.

2) Hold Shift while clicking to paste.

See <https://wiki.debian.org/NewInStretch#Changes> for more on that
change.

[toc] | [prev] | [next] | [standalone]

#245056

On Sun, 6 Feb 2022 09:17:35 -0500
Greg Wooledge <greg@wooledge.org> wrote:

> On Sun, Feb 06, 2022 at 11:25:36AM +0100, Thomas Schmitt wrote:
> > Hi,
> > 
> > José Luis González wrote:
> > > 2. Copy and paste in X don't work anymore by selecting and clicking on
> > > mouse button 2.
> > 
> > "bracketed paste", maybe ?
> 
> Depends on where he's pasting.  Bracketed paste doesn't actually stop
> middle-click pastes from working in bash in a terminal; it just makes
> it look weird, and requires a confirming Enter keypress if you paste
> commands with newlines in them.
> 
> José, *where* are you trying to paste, that isn't working?  At a bash
> prompt?  Inside an editor running in a terminal?  Inside an editor
> that is a GUI program?  Inside some other GUI program like a web
> browser?

From XFCE's to XFCE's terminal emulator, for instance. Also, I tried now from the terminal to Sylpheed (the window where I'm composing this message), and from Sylpheed to Sylpheed (same window text edit widget).

[toc] | [prev] | [next] | [standalone]

#245033

On Sun, Feb 06, 2022 at 11:58:08AM +0100, José Luis González wrote:
> Hi,
> 
> Upon upgrading to Debian 11 several things broke.
> 
> The two that come to my attention now are:
> 
> 1. System time is one hour more than it should. Timezone (as set by
> tzdata) is correct.
> 

Hi 

System time:  what time does the motherboard think it is - so BIOS / firmware?

If you set the time using the date command / a systems setting app
and then run 

	hwclock --systohc

what happens?

hwclock is a small utility to set the hardware clock.

[This way round is system time -> hardware clock or you can do 

	hwclock --hctosys 

to set the other way round.]

Is the system dual booting with another OS which assumes that it has 
control of the clock (usually Windows and setting local timezones
with daylight saving time)?

Hope this helps, any more details you can give may be helpful.

With every good wish, as ever,

Andy Cater

> 2. Copy and paste in X don't work anymore by selecting and clicking on
> mouse button 2.
> 
> I'm running XFCE, if it is of any help.
> 

[toc] | [prev] | [next] | [standalone]

#245057

On Sun, 6 Feb 2022 11:20:37 +0000
"Andrew M.A. Cater" <amacater@einval.com> wrote:

> On Sun, Feb 06, 2022 at 11:58:08AM +0100, José Luis González wrote:
> > Hi,
> > 
> > Upon upgrading to Debian 11 several things broke.
> > 
> > The two that come to my attention now are:
> > 
> > 1. System time is one hour more than it should. Timezone (as set by
> > tzdata) is correct.
> > 
> 
> Hi 

Hi Andrew,

Thanks for stepping in.

> System time:  what time does the motherboard think it is - so BIOS / firmware?

It seems date was set for localtime at the BIOS, so I have updated it to UTC so that it works with Debian.

> Is the system dual booting with another OS which assumes that it has 
> control of the clock (usually Windows and setting local timezones
> with daylight saving time)?

No, the system only has Debian. No dual booting.

> Hope this helps, any more details you can give may be helpful.

It seems with the BIOS adjust it's running right. Thanks for your input. You made me realize what it was.

[toc] | [prev] | [next] | [standalone]

#245034

[Multipart message — attachments visible in raw view] — view raw

* 2022-02-06 11:58:08+0100, José Luis González wrote:

> 1. System time is one hour more than it should. Timezone (as set by
> tzdata) is correct.

Nowadays "timedatectl" is used to configure time. Run the command
without arguments first. Then see its manual page and perhaps use some
of the following subcommands:

    timedatectl set-timezone [...]
    timedatectl set-local-rct [...]
    timedatectl set-time [...]
    timedatectl set-ntp [...]
    
-- 
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462

[toc] | [prev] | [next] | [standalone]

#245038

On Sun, Feb 06, 2022 at 02:00:21PM +0200, Teemu Likonen wrote:
> * 2022-02-06 11:58:08+0100, José Luis González wrote:
> 
> > 1. System time is one hour more than it should. Timezone (as set by
> > tzdata) is correct.
> 
> Nowadays "timedatectl" is used to configure time.

Strongly disagree.  I mean, it *could* be... but you state it like it's
an absolute imperative.

Many of us still use the traditional tools.

My first question for José is: what does the date command *actually*
say?  (Follow-ups: What time zone are you in?  How did you configure
the time zone?  Are you running an NTP daemon?  If so, which one, and
what does "ntpq -p" report?)

E.g. for me, I am in the US/Eastern time zone (now called America/New_York)
and I'm running the "ntp" daemon.  I don't have the TZ variable set.
So, my setup looks like this:

unicorn:~$ echo "$TZ"

unicorn:~$ cat /etc/timezone
America/New_York
unicorn:~$ ls -ld /etc/localtime
lrwxrwxrwx 1 root root 36 Oct 27 07:16 /etc/localtime -> /usr/share/zoneinfo/America/New_York
unicorn:~$ dpkg -l ntp | tail -1
ii  ntp            1:4.2.8p15+dfsg-1 amd64        Network Time Protocol daemon and utility programs
unicorn:~$ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000   0.000
 1.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000   0.000
 2.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000   0.000
 3.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000   0.000
-vps-d455c3c7.vp 91.189.91.157    3 u  759 1024  377   74.942   +1.701   0.819
+172.106.167.46  209.51.161.238   2 u  543 1024  377   62.995   +1.964   1.041
-time.nullrouten 132.163.97.1     2 u  485 1024  377   93.519   +0.097   0.823
*time-sjc.0xt.ca 17.253.4.125     2 u  845 1024  377   96.872   +0.563   2.251
+li1210-167.memb 66.220.9.122     2 u  566 1024  377   96.236   +0.522  10.941
-clock.fmt.he.ne .CDMA.           1 u  968 1024  377   93.254   -1.045   7.428
unicorn:~$ date
Sun Feb  6 09:05:43 EST 2022

Note in particular that the timezone is configured in *two* different
places using two different mechanisms.  Some programs use one, and some
use the other, so you need to do both.  "Welcome to Unix, kid."  (The
Debian installer takes care of this for you, if you choose the time zone
correctly during installation.)

Andrew's reply about hwclock is also relevant if José is dual-booting
with another operating system.  Are you doing that, José?

[toc] | [prev] | [next] | [standalone]

#245046

On Sun 06 Feb 2022 at 09:12:01 (-0500), Greg Wooledge wrote:
> On Sun, Feb 06, 2022 at 02:00:21PM +0200, Teemu Likonen wrote:
> > * 2022-02-06 11:58:08+0100, José Luis González wrote:
> > 
> > > 1. System time is one hour more than it should. Timezone (as set by
> > > tzdata) is correct.
> > 
> > Nowadays "timedatectl" is used to configure time.
> 
> Strongly disagree.  I mean, it *could* be... but you state it like it's
> an absolute imperative.
> 
> Many of us still use the traditional tools.
> 
> My first question for José is: what does the date command *actually*
> say?  (Follow-ups: What time zone are you in?  How did you configure
> the time zone?  Are you running an NTP daemon?  If so, which one, and
> what does "ntpq -p" report?)
> 
> E.g. for me, I am in the US/Eastern time zone (now called America/New_York)
> and I'm running the "ntp" daemon.  I don't have the TZ variable set.
> So, my setup looks like this:
> 
> unicorn:~$ echo "$TZ"
> 
> unicorn:~$ cat /etc/timezone
> America/New_York
> unicorn:~$ ls -ld /etc/localtime
> lrwxrwxrwx 1 root root 36 Oct 27 07:16 /etc/localtime -> /usr/share/zoneinfo/America/New_York
> unicorn:~$ dpkg -l ntp | tail -1
> ii  ntp            1:4.2.8p15+dfsg-1 amd64        Network Time Protocol daemon and utility programs
> unicorn:~$ ntpq -p
>      remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
>  0.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000   0.000
>  1.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000   0.000
>  2.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000   0.000
>  3.debian.pool.n .POOL.          16 p    -   64    0    0.000   +0.000   0.000
> -vps-d455c3c7.vp 91.189.91.157    3 u  759 1024  377   74.942   +1.701   0.819
> +172.106.167.46  209.51.161.238   2 u  543 1024  377   62.995   +1.964   1.041
> -time.nullrouten 132.163.97.1     2 u  485 1024  377   93.519   +0.097   0.823
> *time-sjc.0xt.ca 17.253.4.125     2 u  845 1024  377   96.872   +0.563   2.251
> +li1210-167.memb 66.220.9.122     2 u  566 1024  377   96.236   +0.522  10.941
> -clock.fmt.he.ne .CDMA.           1 u  968 1024  377   93.254   -1.045   7.428
> unicorn:~$ date
> Sun Feb  6 09:05:43 EST 2022
> 
> Note in particular that the timezone is configured in *two* different
> places using two different mechanisms.  Some programs use one, and some
> use the other, so you need to do both.  "Welcome to Unix, kid."  (The
> Debian installer takes care of this for you, if you choose the time zone
> correctly during installation.)
> 
> Andrew's reply about hwclock is also relevant if José is dual-booting
> with another operating system.  Are you doing that, José?

It does seem quite likely that there's a misunderstanding over
timezones, as the OP is posting from +1 and their clock is one
hour in error. They may have to decide whether to run the RTC
in UT (in general the only sensible choice) or Local Time.

(I'm not sure whether DST in relevant at this time of year in
this timezone, unless they observe it in Tristan da Cunha.)

That said, I notice you have ntp installed. Does that mean that
you're keeping your time synchronised with ntp and, if so, what
do you do about systemd-timesyncd, which I understand is enabled
by default since several Debian versions ago.

About setting   hwclock --systohc   directly, I see two problems:
the system's timekeeper might merely set it again itself, losing
whatever you set it to, and also it screws up any calibrations
being made on the RTC's drift.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#245050

On Sun, Feb 06, 2022 at 10:42:31AM -0600, David Wright wrote:
> That said, I notice you have ntp installed. Does that mean that
> you're keeping your time synchronised with ntp and, if so, what
> do you do about systemd-timesyncd, which I understand is enabled
> by default since several Debian versions ago.

If an NTP package is installed, systemd-timesyncd is not used.  It
just never starts.

On my system, it's not even installed.

After digging around a bit, I think Debian has changed something on me,
which I didn't notice until now.

In older versions of Debian, systemd-timesyncd and ntp (or chrony, etc.)
would coexist.  systemd-timesyncd.service was configured so that the
daemon wouldn't be started if any of the other NTP daemons existed on
the system.

I can no longer see that in the systemd-timesyncd.service file (which
I'm viewing as
<https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/units/systemd-timesyncd.service.in>
because it's not on my system).

Instead, the ntp and systemd-timesyncd *packages* now appear to have

Provides: time-daemon

which might make them mutually exclusive.

[toc] | [prev] | [next] | [standalone]

#245053

On Sun 06 Feb 2022 at 12:09:39 -0500, Greg Wooledge wrote:

> On Sun, Feb 06, 2022 at 10:42:31AM -0600, David Wright wrote:
> > That said, I notice you have ntp installed. Does that mean that
> > you're keeping your time synchronised with ntp and, if so, what
> > do you do about systemd-timesyncd, which I understand is enabled
> > by default since several Debian versions ago.
> 
> If an NTP package is installed, systemd-timesyncd is not used.  It
> just never starts.
> 
> On my system, it's not even installed.
> 
> After digging around a bit, I think Debian has changed something on me,
> which I didn't notice until now.
> 
> In older versions of Debian, systemd-timesyncd and ntp (or chrony, etc.)
> would coexist.  systemd-timesyncd.service was configured so that the
> daemon wouldn't be started if any of the other NTP daemons existed on
> the system.
> 
> I can no longer see that in the systemd-timesyncd.service file (which
> I'm viewing as
> <https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/units/systemd-timesyncd.service.in>
> because it's not on my system).
> 
> Instead, the ntp and systemd-timesyncd *packages* now appear to have
> 
> Provides: time-daemon
> 
> which might make them mutually exclusive.

It does. Installation of chrony or ntp removeds the traditional
systemd-timesyncd package.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#245054

Thanks everybody for your input.

Does anybody know why the X copy/paste issue is happening? So far I
have only got help with time.


On Sun, 6 Feb 2022 18:54:26 +0000
Brian <ad44@cityscape.co.uk> wrote:

> On Sun 06 Feb 2022 at 12:09:39 -0500, Greg Wooledge wrote:
> 
> > On Sun, Feb 06, 2022 at 10:42:31AM -0600, David Wright wrote:
> > > That said, I notice you have ntp installed. Does that mean that
> > > you're keeping your time synchronised with ntp and, if so, what
> > > do you do about systemd-timesyncd, which I understand is enabled
> > > by default since several Debian versions ago.
> > 
> > If an NTP package is installed, systemd-timesyncd is not used.  It
> > just never starts.
> > 
> > On my system, it's not even installed.
> > 
> > After digging around a bit, I think Debian has changed something on me,
> > which I didn't notice until now.
> > 
> > In older versions of Debian, systemd-timesyncd and ntp (or chrony, etc.)
> > would coexist.  systemd-timesyncd.service was configured so that the
> > daemon wouldn't be started if any of the other NTP daemons existed on
> > the system.
> > 
> > I can no longer see that in the systemd-timesyncd.service file (which
> > I'm viewing as
> > <https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/units/systemd-timesyncd.service.in>
> > because it's not on my system).
> > 
> > Instead, the ntp and systemd-timesyncd *packages* now appear to have
> > 
> > Provides: time-daemon
> > 
> > which might make them mutually exclusive.
> 
> It does. Installation of chrony or ntp removeds the traditional
> systemd-timesyncd package.
> 
> -- 
> Brian.
> 

[toc] | [prev] | [next] | [standalone]

#245055

On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote:
> Thanks everybody for your input.
> 
> Does anybody know why the X copy/paste issue is happening? So far I
> have only got help with time.

https://lists.debian.org/debian-user/2022/02/msg00144.html

https://lists.debian.org/debian-user/2022/02/msg00151.html

[toc] | [prev] | [next] | [standalone]

#245059

On Sun, 6 Feb 2022 15:59:34 -0500
Greg Wooledge <greg@wooledge.org> wrote:

> On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote:
> > Thanks everybody for your input.
> > 
> > Does anybody know why the X copy/paste issue is happening? So far I
> > have only got help with time.
> 
> https://lists.debian.org/debian-user/2022/02/msg00144.html
> 
> https://lists.debian.org/debian-user/2022/02/msg00151.html

Thanks for the tip, but I'm afraid it isn't bracketed paste. I'm suffering from this everywhere, not only in bash.

[toc] | [prev] | [next] | [standalone]

#245060

On Sun, Feb 06, 2022 at 11:58:52PM +0100, José Luis González wrote:
> On Sun, 6 Feb 2022 15:59:34 -0500
> Greg Wooledge <greg@wooledge.org> wrote:
> 
> > On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote:
> > > Thanks everybody for your input.
> > > 
> > > Does anybody know why the X copy/paste issue is happening? So far I
> > > have only got help with time.
> > 
> > https://lists.debian.org/debian-user/2022/02/msg00144.html
> > 
> > https://lists.debian.org/debian-user/2022/02/msg00151.html
> 
> Thanks for the tip, but I'm afraid it isn't bracketed paste. I'm suffering from this everywhere, not only in bash.

What symptom are you actually seeing?  What happens when you click the
middle button, while focus is on a terminal sitting at a bash prompt,
and while something has been selected?

Do you get a mangled paste?  Do you get a correct paste, except that it's
in "inverse video"?  Do you get nothing at all?

If it's nothing at all, how sure are you that it's not a hardware problem?
Have you tried a different mouse?  Have you tried using xev to see whether
the Button2 up/down events are actually being received by the X server?

[toc] | [prev] | [next] | [standalone]

#245064

On Sun 06 Feb 2022 at 18:03:42 (-0500), Greg Wooledge wrote:
> On Sun, Feb 06, 2022 at 11:58:52PM +0100, José Luis González wrote:
> > On Sun, 6 Feb 2022 15:59:34 -0500 Greg Wooledge wrote:
> > > On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote:
> > > > 
> > > > Does anybody know why the X copy/paste issue is happening? So far I
> > > > have only got help with time.
> > > 
> > > https://lists.debian.org/debian-user/2022/02/msg00144.html
> > > 
> > > https://lists.debian.org/debian-user/2022/02/msg00151.html
> > 
> > Thanks for the tip, but I'm afraid it isn't bracketed paste. I'm suffering from this everywhere, not only in bash.

Technically, I think you get bracketed paste through anything that
uses readline (the animal that reads ~/.inputrc).

And before what follows, is dragging actually working?

> What symptom are you actually seeing?  What happens when you click the
> middle button, while focus is on a terminal sitting at a bash prompt,
> and while something has been selected?
> 
> Do you get a mangled paste?  Do you get a correct paste, except that it's
> in "inverse video"?  Do you get nothing at all?
> 
> If it's nothing at all, how sure are you that it's not a hardware problem?
> Have you tried a different mouse?  Have you tried using xev to see whether
> the Button2 up/down events are actually being received by the X server?

As a workaround, do the CUA keys work? That is, cutting with ^X,
copying with ^C and pasting with ^V. Are there menus or options
in XFCE for selecting this method?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#245067

On Sun, Feb 06, 2022 at 08:03:55PM -0600, David Wright wrote:
> Technically, I think you get bracketed paste through anything that
> uses readline (the animal that reads ~/.inputrc).

Yes.  Potentailly, at least.

> As a workaround, do the CUA keys work? That is, cutting with ^X,
> copying with ^C and pasting with ^V. Are there menus or options
> in XFCE for selecting this method?

Those won't work for copy/paste in a shell, of course.  They may work
in a GUI application.  Shift-Insert also tends to work for pasting in
many applications, including rxvt-unicode (my terminal emulator) and
xterm, even when sitting at a shell prompt.

[toc] | [prev] | [next] | [standalone]

#245068

On Sun, Feb 06, 2022 at 06:54:26PM +0000, Brian wrote:
>It does. Installation of chrony or ntp removeds the traditional
>systemd-timesyncd package.

I'm somewhat amused by the characterization of systemd-timesyncd as 
"traditional" over ntpd, a program which has existed since the late 80s.

[toc] | [prev] | [next] | [standalone]

#245047

On Sun, 6 Feb 2022 09:12:01 -0500
Greg Wooledge <greg@wooledge.org> wrote:

> My first question for José is: what does the date command *actually*
> say?  (Follow-ups: What time zone are you in?  How did you configure
> the time zone?  Are you running an NTP daemon?  If so, which one, and
> what does "ntpq -p" report?)

If you aren't running an NTP daemon, are you running systemd's time
client, time-sync? What result do you get from

systemctl status time-sync.target

(I have a small herd of Debian boxen. One runs ntpd to synch with the
outside world. All the rest run time-sync and synch on the ntpd box. It
works quiet well.)

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#245049

On Sun 06 Feb 2022 at 09:44:54 -0700, Charles Curley wrote:

> On Sun, 6 Feb 2022 09:12:01 -0500
> Greg Wooledge <greg@wooledge.org> wrote:
> 
> > My first question for José is: what does the date command *actually*
> > say?  (Follow-ups: What time zone are you in?  How did you configure
> > the time zone?  Are you running an NTP daemon?  If so, which one, and
> > what does "ntpq -p" report?)
> 
> If you aren't running an NTP daemon, are you running systemd's time
> client, time-sync? What result do you get from
> 
> systemctl status time-sync.target
> 
> (I have a small herd of Debian boxen. One runs ntpd to synch with the
> outside world. All the rest run time-sync and synch on the ntpd box. It
> works quiet well.)

I have always used chrony. It appears have gained more traction over
ntpd recently.

  https://lists.debian.org/debian-devel/2022/01/msg00172.html
  https://engineering.fb.com/2020/03/18/production-engineering/ntp-service/

-- 
Brian.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web