automake-1.9.6-r5 mask question

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

automake-1.9.6-r5 mask question

Walter Dnes
  I just ran a system update and got the following warning...

!!! The following installed packages are masked:
- sys-devel/automake-1.9.6-r5::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Andreas K. Hüttel <[hidden email]> (2017-10-18)
# sys-devel/automake versions 1.4, 1.5, 1.6, 1.7, 1.8
# have known security vulnerabilities, are broken with
# recent Perl (>=5.26.0), and are not used by anything in
# the Gentoo repository. Please uninstall.

1)  It says that 1.4-to-1.8 have problems.  So why is 1.9.6-r5 masked?

2)  It says that no apps use 1.9.6-r5, but...

[d531][root][~] equery d =sys-devel/automake-1.9.6-r5
 * These packages depend on sys-devel/automake-1.9.6-r5:
mail-mta/ssmtp-2.64-r3 (sys-devel/automake)
net-misc/openrdate-1.2 (=sys-devel/automake-1.9*)

  ssmtp would probably be OK with a higher version, but openrdate
specifically wants automake-1.9*.  The next version upwards in
/usr/portage/sys-devel/automake is 1.10.3-r3

  I currently have 1.9.6-r5 and 1.15.1-r2 and 1.16.1-r1 installed.

--
Walter Dnes <[hidden email]>
I don't run "desktop environments"; I run useful applications

Reply | Threaded
Open this post in threaded view
|

Re: automake-1.9.6-r5 mask question

Jack
On 2019.12.07 19:37, Walter Dnes wrote:

>   I just ran a system update and got the following warning...
>
> !!! The following installed packages are masked:
> - sys-devel/automake-1.9.6-r5::gentoo (masked by: package.mask)
> /usr/portage/profiles/package.mask:
> # Andreas K. Hüttel <[hidden email]> (2017-10-18)
> # sys-devel/automake versions 1.4, 1.5, 1.6, 1.7, 1.8
> # have known security vulnerabilities, are broken with
> # recent Perl (>=5.26.0), and are not used by anything in
> # the Gentoo repository. Please uninstall.
>
> 1)  It says that 1.4-to-1.8 have problems.  So why is 1.9.6-r5 masked?
If you look at package.mask, it does say 1.4 to 1.8 have the  
vulnerability, but it did mask 1.4 through 1.10.  I don't know if it  
was a typo (excluding 1.9 and 1.10 from having problems, or including  
them in the mask.)  Might a bug be warranted?
>
> 2)  It says that no apps use 1.9.6-r5, but...
>
> [d531][root][~] equery d =sys-devel/automake-1.9.6-r5
>  * These packages depend on sys-devel/automake-1.9.6-r5:
> mail-mta/ssmtp-2.64-r3 (sys-devel/automake)
> net-misc/openrdate-1.2 (=sys-devel/automake-1.9*)
Have you tried updating or reinstalling either of those?  Have you  
tried depcleaning automake to see if it agrees with these  
dependencies?  (I'm grabbing at straws, and won't predict any  
particular result.)  That version of ssmtp does not (from the ebuild)  
require any particular version of automake, so might that just be  
because that was the version used to build it?  I don't see openrdate  
in the main tree, so that could be why he missed it.
>
>   ssmtp would probably be OK with a higher version, but openrdate
> specifically wants automake-1.9*.  The next version upwards in
> /usr/portage/sys-devel/automake is 1.10.3-r3
>
>   I currently have 1.9.6-r5 and 1.15.1-r2 and 1.16.1-r1 installed.
I obviously have a very different world file from you, but I've got  
1.11.6-r3, 1.13.4-r2, and 1.16.1-r1 installed.  "emerge -pc automake"  
says two packages need the 1.11, one needs 1.13, and a whole bunch need  
1.16.
>
> --
> Walter Dnes <[hidden email]>
> I don't run "desktop environments"; I run useful applications

Jack
Reply | Threaded
Open this post in threaded view
|

Re: automake-1.9.6-r5 mask question

Marc Joliet
In reply to this post by Walter Dnes
Am Sonntag, 8. Dezember 2019, 01:37:17 CET schrieb Walter Dnes:

>   I just ran a system update and got the following warning...
>
> !!! The following installed packages are masked:
> - sys-devel/automake-1.9.6-r5::gentoo (masked by: package.mask)
> /usr/portage/profiles/package.mask:
> # Andreas K. Hüttel <[hidden email]> (2017-10-18)
> # sys-devel/automake versions 1.4, 1.5, 1.6, 1.7, 1.8
> # have known security vulnerabilities, are broken with
> # recent Perl (>=5.26.0), and are not used by anything in
> # the Gentoo repository. Please uninstall.
>
> 1)  It says that 1.4-to-1.8 have problems.  So why is 1.9.6-r5 masked?
>
> 2)  It says that no apps use 1.9.6-r5, but...
>
> [d531][root][~] equery d =sys-devel/automake-1.9.6-r5
>  * These packages depend on sys-devel/automake-1.9.6-r5:
> mail-mta/ssmtp-2.64-r3 (sys-devel/automake)
> net-misc/openrdate-1.2 (=sys-devel/automake-1.9*)
openrdate does not appear to be in the portage tree (it was removed on
2019-09-17, specifically because of its dependency on automake 1.9).  I
suppose you put it in a local overlay or something?

>   ssmtp would probably be OK with a higher version, but openrdate
> specifically wants automake-1.9*.  The next version upwards in
> /usr/portage/sys-devel/automake is 1.10.3-r3
>
>   I currently have 1.9.6-r5 and 1.15.1-r2 and 1.16.1-r1 installed.

"git log" to the rescue: commit 85fb9e060cbba2053036988833c2affc9bb6d454
("profiles/package.mask: extend automake mask to :1.9") extended the mask
without updating the comment, and refers to https://bugs.gentoo.org/489450,
which I haven't bothered checking.

HTH
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

signature.asc (235 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: automake-1.9.6-r5 mask question

Dale-46
In reply to this post by Walter Dnes
Walter Dnes wrote:

>   I just ran a system update and got the following warning...
>
> !!! The following installed packages are masked:
> - sys-devel/automake-1.9.6-r5::gentoo (masked by: package.mask)
> /usr/portage/profiles/package.mask:
> # Andreas K. Hüttel <[hidden email]> (2017-10-18)
> # sys-devel/automake versions 1.4, 1.5, 1.6, 1.7, 1.8
> # have known security vulnerabilities, are broken with
> # recent Perl (>=5.26.0), and are not used by anything in
> # the Gentoo repository. Please uninstall.
>
> 1)  It says that 1.4-to-1.8 have problems.  So why is 1.9.6-r5 masked?
>
> 2)  It says that no apps use 1.9.6-r5, but...
>
> [d531][root][~] equery d =sys-devel/automake-1.9.6-r5
>  * These packages depend on sys-devel/automake-1.9.6-r5:
> mail-mta/ssmtp-2.64-r3 (sys-devel/automake)
> net-misc/openrdate-1.2 (=sys-devel/automake-1.9*)
>
>   ssmtp would probably be OK with a higher version, but openrdate
> specifically wants automake-1.9*.  The next version upwards in
> /usr/portage/sys-devel/automake is 1.10.3-r3
>
>   I currently have 1.9.6-r5 and 1.15.1-r2 and 1.16.1-r1 installed.
>


There's a couple threads on -dev about masking python 2 stuff.  It
caused quite a bit of controversy.  I don't know if this is related or
not but could it be that some of the packages depend on python 2 OR you
have something set to python 2 only for some reason? 

If you can't find any other reason for this, you may want to check into
those threads to see if it is related.

Dale

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: automake-1.9.6-r5 mask question

Dale-46
Dale wrote:

> Walter Dnes wrote:
>>   I just ran a system update and got the following warning...
>>
>> !!! The following installed packages are masked:
>> - sys-devel/automake-1.9.6-r5::gentoo (masked by: package.mask)
>> /usr/portage/profiles/package.mask:
>> # Andreas K. Hüttel <[hidden email]> (2017-10-18)
>> # sys-devel/automake versions 1.4, 1.5, 1.6, 1.7, 1.8
>> # have known security vulnerabilities, are broken with
>> # recent Perl (>=5.26.0), and are not used by anything in
>> # the Gentoo repository. Please uninstall.
>>
>> 1)  It says that 1.4-to-1.8 have problems.  So why is 1.9.6-r5 masked?
>>
>> 2)  It says that no apps use 1.9.6-r5, but...
>>
>> [d531][root][~] equery d =sys-devel/automake-1.9.6-r5
>>  * These packages depend on sys-devel/automake-1.9.6-r5:
>> mail-mta/ssmtp-2.64-r3 (sys-devel/automake)
>> net-misc/openrdate-1.2 (=sys-devel/automake-1.9*)
>>
>>   ssmtp would probably be OK with a higher version, but openrdate
>> specifically wants automake-1.9*.  The next version upwards in
>> /usr/portage/sys-devel/automake is 1.10.3-r3
>>
>>   I currently have 1.9.6-r5 and 1.15.1-r2 and 1.16.1-r1 installed.
>>
>
> There's a couple threads on -dev about masking python 2 stuff.  It
> caused quite a bit of controversy.  I don't know if this is related or
> not but could it be that some of the packages depend on python 2 OR you
> have something set to python 2 only for some reason? 
>
> If you can't find any other reason for this, you may want to check into
> those threads to see if it is related.
>
> Dale
>
> :-)  :-) 
>

Sorry. I meant to reply to your other thread.  When reading previous,
apply it to that thread instead of this one. 

Sorry.

Dale

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: automake-1.9.6-r5 mask question

Walter Dnes
In reply to this post by Marc Joliet
On Sun, Dec 08, 2019 at 02:13:47AM +0100, Marc Joliet wrote
>
> openrdate does not appear to be in the portage tree (it was removed on
> 2019-09-17, specifically because of its dependency on automake 1.9).
> I suppose you put it in a local overlay or something?

=======================================================
[i660][waltdnes][~] emerge -pv openrdate

These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds to satisfy "openrdate".
=======================================================

  That explains that.  "net-misc/rdate-1.4-r4" shows up if I run
emerge -pv rdate

  I have a local script that syncs my machine like so...

[i660][waltdnes][~] cat bin/settime
#!/bin/bash
date
/usr/bin/sudo /usr/bin/openrdate -n -s ca.pool.ntp.org
/usr/bin/sudo /sbin/hwclock --systohc
date

...with appropriate entries in /etc/sudoers.d  The "-n" parameter says
"Use SNTP (RFC 2030) instead of the RFC 868 time protocol."  "-n" isn't
mentioned in https://linux.die.net/man/1/rdate  This brings up the
question... is "rdate" a drop-in substitute for "openrdate"?

--
Walter Dnes <[hidden email]>
I don't run "desktop environments"; I run useful applications

Reply | Threaded
Open this post in threaded view
|

What ntp/sntp client do people use?

Walter Dnes
On Sun, Dec 08, 2019 at 01:38:59AM -0500, Walter Dnes wrote

> question... is "rdate" a drop-in substitute for "openrdate"?

  Answering my own question... big fat NO.

[i660][root][~] openrdate -s -n ca.pool.ntp.org (works fine)

[i660][root][~] openrdate -s ca.pool.ntp.org (hangs and sits there)

[i660][root][~] rdate -s ca.pool.ntp.org
rdate: couldn't connect to host ca.pool.ntp.org: Connection refused

  Apparently "openrdate -n" selects RFC2030 protocol.  Otherwise, it
defaults to RFC868.  That appears to be rdate's only protocol.  So are
there any public RFC868 servers?  Or are there any RFC2030 client
programs other than openrdate?  What do people here use?

--
Walter Dnes <[hidden email]>
I don't run "desktop environments"; I run useful applications

Reply | Threaded
Open this post in threaded view
|

Re: What ntp/sntp client do people use?

Mick-10
On Tuesday, 10 December 2019 06:16:50 GMT Walter Dnes wrote:

> On Sun, Dec 08, 2019 at 01:38:59AM -0500, Walter Dnes wrote
>
> > question... is "rdate" a drop-in substitute for "openrdate"?
>
>   Answering my own question... big fat NO.
>
> [i660][root][~] openrdate -s -n ca.pool.ntp.org (works fine)
>
> [i660][root][~] openrdate -s ca.pool.ntp.org (hangs and sits there)
>
> [i660][root][~] rdate -s ca.pool.ntp.org
> rdate: couldn't connect to host ca.pool.ntp.org: Connection refused
>
>   Apparently "openrdate -n" selects RFC2030 protocol.  Otherwise, it
> defaults to RFC868.  That appears to be rdate's only protocol.  So are
> there any public RFC868 servers?  Or are there any RFC2030 client
> programs other than openrdate?  What do people here use?
I no longer use rdate and SNTP.  I use chronyd which has no problem
synchronising with various NTP servers and is suitable for systems which are
online intermittently, like laptops.

--
Regards,

Mick

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: What ntp/sntp client do people use?

Peter Humphrey-3
On Tuesday, 10 December 2019 07:56:17 GMT Mick wrote:

> I no longer use rdate and SNTP.  I use chronyd which has no problem
> synchronising with various NTP servers and is suitable for systems which are
> online intermittently, like laptops.

What he said.

--
Regards,
Peter.




Reply | Threaded
Open this post in threaded view
|

Re: What ntp/sntp client do people use?

David Haller-5
In reply to this post by Walter Dnes
Hello,

On Tue, 10 Dec 2019, Walter Dnes wrote:
>there any public RFC868 servers?  Or are there any RFC2030 client
>programs other than openrdate?  What do people here use?

I use net-misc/ntp. As a daemon and if needed ntpdate/sntp to set the time.

-dnh

--
Q: Why is it that New Jersey got all the toxic waste dumps and California
   got all the lawyers?
A: New Jersey had first choice.                                -- unknown

Reply | Threaded
Open this post in threaded view
|

Re: What ntp/sntp client do people use?

Dale-46
In reply to this post by Peter Humphrey-3
Peter Humphrey wrote:
> On Tuesday, 10 December 2019 07:56:17 GMT Mick wrote:
>
>> I no longer use rdate and SNTP.  I use chronyd which has no problem
>> synchronising with various NTP servers and is suitable for systems which are
>> online intermittently, like laptops.
> What he said.
>


+1  I think I used ntpdate years ago.  Can't recall why I switched but
something wasn't working right.  People here recommended chrony and once
set up, its worked ever since.  OP, if you haven't tried it yet, may be
worth giving it a test run. 

Dale

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: What ntp/sntp client do people use?

Walter Dnes
On Tue, Dec 10, 2019 at 03:19:16AM -0600, Dale wrote

>   I think I used ntpdate years ago.  Can't recall why I switched but
> something wasn't working right.  People here recommended chrony and once
> set up, its worked ever since.  OP, if you haven't tried it yet, may be
> worth giving it a test run.

  Now what?  I'm willing to RTFM, but I can't FTFM (Find the F******
Manual).

=======================================================================

strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version
   /usr/bin/chronyc
   /usr/sbin/chronyd

>>> Installing (1 of 1) net-misc/chrony-3.5-r2::gentoo

>>> Recording net-misc/chrony in "world" favorites file...
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.
[i660][root][~] man chrony
No manual entry for chrony
[i660][root][~] info chrony
info: No menu item 'chrony' in node '(dir)Top'
[i660][root][~] emerge --unmerge chrony

=======================================================================

  Has RFC868 been deprecated everywhere, or is it just ca.pool.ntp.org
that won't listen to it?

--
Walter Dnes <[hidden email]>
I don't run "desktop environments"; I run useful applications

Reply | Threaded
Open this post in threaded view
|

Re: What ntp/sntp client do people use?

Dale-46
Walter Dnes wrote:

> On Tue, Dec 10, 2019 at 03:19:16AM -0600, Dale wrote
>
>>   I think I used ntpdate years ago.  Can't recall why I switched but
>> something wasn't working right.  People here recommended chrony and once
>> set up, its worked ever since.  OP, if you haven't tried it yet, may be
>> worth giving it a test run.
>   Now what?  I'm willing to RTFM, but I can't FTFM (Find the F******
> Manual).
>
> =======================================================================
>
> strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version
>    /usr/bin/chronyc
>    /usr/sbin/chronyd
>

I have no idea what this part is doing. 

>>>> Installing (1 of 1) net-misc/chrony-3.5-r2::gentoo
>>>> Recording net-misc/chrony in "world" favorites file...
>>>> Auto-cleaning packages...
>>>> No outdated packages were found on your system.
>  * GNU info directory index is up-to-date.
> [i660][root][~] man chrony
> No manual entry for chrony
> [i660][root][~] info chrony
> info: No menu item 'chrony' in node '(dir)Top'
> [i660][root][~] emerge --unmerge chrony
>
> =======================================================================
>
>   Has RFC868 been deprecated everywhere, or is it just ca.pool.ntp.org
> that won't listen to it?
>


When I set up chrony, I just set up the config file and then started the
service.  After that, it just runs and does its work.  If it helps, this
is my chrony.conf file.



root@fireball / # cat /etc/chrony/chrony.conf
# Use public NTP servers from the pool.ntp.org project.
#pool pool.ntp.org iburst

### SPECIFY YOUR NTP SERVERS
# Most computers using chrony will send measurement requests to one or
# more 'NTP servers'.  You will probably find that your Internet Service
# Provider or company have one or more NTP servers that you can specify.
# Failing that, there are a lot of public NTP servers.  There is a list
# you can access at http://support.ntp.org/bin/view/Servers/WebHome or
# you can use servers from the pool.ntp.org project.

server  64.6.144.6
server  67.159.5.90
server  67.59.168.233
server  204.62.14.98

server  69.50.219.51
server  209.114.111.1



# Record the rate at which the system clock gains/losses time.
driftfile /var/lib/chrony/drift

# Allow the system clock to be stepped in the first three updates
# if its offset is larger than 1 second.
makestep 1.0 3

# Enable kernel synchronization of the real-time clock (RTC).
rtcsync
root@fireball / #


After that, just do a /etc/init.d/chronyd start and it will get the
clock synced and keep it that way. 

I found the manual here.  It was the first hit on google for me. 

https://chrony.tuxfamily.org/documentation.html

I'm no chrony expert by any measure.  For me, the hardest part was
finding the fastest servers.  I think I use that mirrorselect tool, I
think. Its been a while.

Hope that helps. 

Dale

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: What ntp/sntp client do people use?

Adam Carter
chrony on the "server" to sync from the Internet and systemd-timesyncd on the others to sync from the server.
Reply | Threaded
Open this post in threaded view
|

Re: What ntp/sntp client do people use?

Mick-10
In reply to this post by Walter Dnes
On Wednesday, 11 December 2019 04:59:08 GMT Walter Dnes wrote:

> On Tue, Dec 10, 2019 at 03:19:16AM -0600, Dale wrote
>
> >   I think I used ntpdate years ago.  Can't recall why I switched but
> >
> > something wasn't working right.  People here recommended chrony and once
> > set up, its worked ever since.  OP, if you haven't tried it yet, may be
> > worth giving it a test run.
>
>   Now what?  I'm willing to RTFM, but I can't FTFM (Find the F******
> Manual).
Have a look at:

man chronyd

It runs as a daemon.  The command line utility to interefere with it is
detailed in:

man chronyc


Typically I set /etc/chrony/chrony.conf and run it as a default service.  Upon
setting it up I run 'chronyc sources -v' a couple of times to make sure it is
working as desired.  For laptops which are not online 24-7 it is worth adding
'iburst' after the address of a time server to allow the clock to adjust fast
at boot.  Additional information can be found here:

$ ls -la /usr/share/doc/chrony-3.5-r2/
total 72
drwxr-xr-x   3 root root  4096 Nov  2 09:27 .
drwxr-xr-x 826 root root 36864 Dec  7 16:42 ..
-rw-r--r--   1 root root  7942 Nov  2 09:27 FAQ.bz2
-rw-r--r--   1 root root  9844 Nov  2 09:27 NEWS.bz2
-rw-r--r--   1 root root  3167 Nov  2 09:27 README.bz2
drwxr-xr-x   2 root root  4096 Nov  2 09:27 examples

HTH.

--
Regards,

Mick

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

[SOLVED] What ntp/sntp client do people use?

Walter Dnes
In reply to this post by Dale-46
On Tue, Dec 10, 2019 at 11:14:48PM -0600, Dale wrote

> Walter Dnes wrote:
>
> > =======================================================================
> >
> > strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version
> >    /usr/bin/chronyc
> >    /usr/sbin/chronyd
> >
>
> I have no idea what this part is doing.

  That is approaching the end of the "emerge chrony" process.  I wanted
to show that I've installed chrony.

>
> >>>> Installing (1 of 1) net-misc/chrony-3.5-r2::gentoo
> >>>> Recording net-misc/chrony in "world" favorites file...
> >>>> Auto-cleaning packages...
> >>>> No outdated packages were found on your system.
> >  * GNU info directory index is up-to-date.
> > [i660][root][~] man chrony
> > No manual entry for chrony
> > [i660][root][~] info chrony
> > info: No menu item 'chrony' in node '(dir)Top'
> > [i660][root][~] emerge --unmerge chrony
> >
> > =======================================================================

> I found the manual here.  It was the first hit on google for me.
>
> https://chrony.tuxfamily.org/documentation.html

> Hope that helps.

  Thanks.  From that webpage...

> 2.7. Does chronyd have an ntpdate mode?
>
> Yes. With the -q option chronyd will set the system clock once and
> exit. With the -Q option it will print the measured offset without
> setting the clock. If you don't want to use a configuration file,
> NTP servers can be specified on the command line. For example:
>
> # chronyd -q 'pool pool.ntp.org iburst'

  So I ran a script 3 times...

#!/bin/bash
date
chronyd -q 'pool ca.pool.ntp.org iburst'
date

...and I got...

[i660][root][~] ./settime
Wed 11 Dec 2019 12:18:45 PM EST
2019-12-11T17:18:45Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH -IPV6 -DEBUG)
2019-12-11T17:18:50Z System clock wrong by 0.574369 seconds (step)
2019-12-11T17:18:51Z chronyd exiting
Wed 11 Dec 2019 12:18:51 PM EST
[i660][root][~] ./settime
Wed 11 Dec 2019 12:19:06 PM EST
2019-12-11T17:19:06Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH -IPV6 -DEBUG)
2019-12-11T17:19:12Z System clock wrong by -0.000421 seconds (step)
2019-12-11T17:19:12Z chronyd exiting
Wed 11 Dec 2019 12:19:12 PM EST
[i660][root][~] ./settime
Wed 11 Dec 2019 12:19:18 PM EST
2019-12-11T17:19:18Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH -IPV6 -DEBUG)
2019-12-11T17:19:23Z System clock wrong by -0.000084 seconds (step)
2019-12-11T17:19:23Z chronyd exiting
Wed 11 Dec 2019 12:19:23 PM EST

  I'm not totally happy that I have to run it 3 times, but I can do that
in the script.  I prefer openrdate's approach where it gets the exact
time once.  What's with this "step" fetish?

--
Walter Dnes <[hidden email]>
I don't run "desktop environments"; I run useful applications

Reply | Threaded
Open this post in threaded view
|

Re: [SOLVED] What ntp/sntp client do people use?

Dale-46
Walter Dnes wrote:

> On Tue, Dec 10, 2019 at 11:14:48PM -0600, Dale wrote
>> Walter Dnes wrote:
>>
>>> =======================================================================
>>>
>>> strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version
>>>    /usr/bin/chronyc
>>>    /usr/sbin/chronyd
>>>
>> I have no idea what this part is doing.
>   That is approaching the end of the "emerge chrony" process.  I wanted
> to show that I've installed chrony.
>
>>>>>> Installing (1 of 1) net-misc/chrony-3.5-r2::gentoo
>>>>>> Recording net-misc/chrony in "world" favorites file...
>>>>>> Auto-cleaning packages...
>>>>>> No outdated packages were found on your system.
>>>  * GNU info directory index is up-to-date.
>>> [i660][root][~] man chrony
>>> No manual entry for chrony
>>> [i660][root][~] info chrony
>>> info: No menu item 'chrony' in node '(dir)Top'
>>> [i660][root][~] emerge --unmerge chrony
>>>
>>> =======================================================================
>> I found the manual here.  It was the first hit on google for me.
>>
>> https://chrony.tuxfamily.org/documentation.html
>> Hope that helps.
>   Thanks.  From that webpage...
>
>> 2.7. Does chronyd have an ntpdate mode?
>>
>> Yes. With the -q option chronyd will set the system clock once and
>> exit. With the -Q option it will print the measured offset without
>> setting the clock. If you don't want to use a configuration file,
>> NTP servers can be specified on the command line. For example:
>>
>> # chronyd -q 'pool pool.ntp.org iburst'
>   So I ran a script 3 times...
>
> #!/bin/bash
> date
> chronyd -q 'pool ca.pool.ntp.org iburst'
> date
>
> ...and I got...
>
> [i660][root][~] ./settime
> Wed 11 Dec 2019 12:18:45 PM EST
> 2019-12-11T17:18:45Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH -IPV6 -DEBUG)
> 2019-12-11T17:18:50Z System clock wrong by 0.574369 seconds (step)
> 2019-12-11T17:18:51Z chronyd exiting
> Wed 11 Dec 2019 12:18:51 PM EST
> [i660][root][~] ./settime
> Wed 11 Dec 2019 12:19:06 PM EST
> 2019-12-11T17:19:06Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH -IPV6 -DEBUG)
> 2019-12-11T17:19:12Z System clock wrong by -0.000421 seconds (step)
> 2019-12-11T17:19:12Z chronyd exiting
> Wed 11 Dec 2019 12:19:12 PM EST
> [i660][root][~] ./settime
> Wed 11 Dec 2019 12:19:18 PM EST
> 2019-12-11T17:19:18Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH -IPV6 -DEBUG)
> 2019-12-11T17:19:23Z System clock wrong by -0.000084 seconds (step)
> 2019-12-11T17:19:23Z chronyd exiting
> Wed 11 Dec 2019 12:19:23 PM EST
>
>   I'm not totally happy that I have to run it 3 times, but I can do that
> in the script.  I prefer openrdate's approach where it gets the exact
> time once.  What's with this "step" fetish?
>


As Mick pointed out, it is really intended to be run as a service.  You
start it and over time it adjusts the time until it is accurate.  I
don't think it is intended to run as a command and then not run again
since most clocks drift which is why things like chrony and *date are
needed.  It adjusts the time in steps.  It's not a fetish, it's how it
works.  When I used ntpdate, it did the same way.  As far as I know, all
the programs that set the clocks and keep them from drifting off are
done in steps. 

I don't know how openrdate works but for chrony, set up the config file
and then /etc/init.d/chronyd start.  After a bit, you can check to see
how close it is.  If things are working well enough, don't forget to add
it to a runlevel so that it starts when you boot up.  This is what mine
shows and its been running as a service since my last reboot about 13
days ago. 


root@fireball / # chronyc sources -v
210 Number of sources = 6

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current synced, '+' = combined , '-' = not
combined,
| /   '?' = unreachable, 'x' = time may be in error, '~' = time too
variable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted
offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured
offset,
||                                \     |          |  zzzz = estimated
error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last
sample              
===============================================================================
^+ triangle.kansas.net           3  10   251   64m    -36us[ -937us]
+/-  132ms
^? B1-66ER.matrix.gs             0  10     0     -     +0ns[   +0ns]
+/-    0ns
^? eris.kallisti.us              0  10     0     -     +0ns[   +0ns]
+/-    0ns
^? 204-62-14-98.static.6syn>     0  10     0     -     +0ns[   +0ns]
+/-    0ns
^? 69.50.219.51                  0  10     0     -     +0ns[   +0ns]
+/-    0ns
^* bindcat.fhsu.edu              2  10   377   445   -433us[-1298us]
+/-   75ms
root@fireball / #


It appears that my clock is accurate somewhere between 75 and 132ms.  It
also seems I need to update my server list since some are not working. 

Dale

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: What ntp/sntp client do people use?

Marc Joliet
In reply to this post by Walter Dnes
Am Mittwoch, 11. Dezember 2019, 05:59:08 CET schrieb Walter Dnes:

> On Tue, Dec 10, 2019 at 03:19:16AM -0600, Dale wrote
>
> >   I think I used ntpdate years ago.  Can't recall why I switched but
> >
> > something wasn't working right.  People here recommended chrony and once
> > set up, its worked ever since.  OP, if you haven't tried it yet, may be
> > worth giving it a test run.
>
>   Now what?  I'm willing to RTFM, but I can't FTFM (Find the F******
> Manual).
>
[...]
> [i660][root][~] man chrony
> No manual entry for chrony
> [i660][root][~] info chrony
> info: No menu item 'chrony' in node '(dir)Top'
> [i660][root][~] emerge --unmerge chrony
[...]

I know it's easy to forget, but "apropos" is a thing ;-) :

% apropos chrony
chrony.conf (5)      - chronyd configuration file
chronyc (1)          - command-line interface for chrony daemon
chronyd (8)          - chrony daemon

HTH
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

signature.asc (235 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [SOLVED] What ntp/sntp client do people use?

Walter Dnes
In reply to this post by Dale-46
On Wed, Dec 11, 2019 at 08:37:10PM +1100, Adam Carter wrote
> chrony on the "server" to sync from the Internet and systemd-timesyncd
> on the others to sync from the server.

  Sounds like something Lennart came up with.

On Wed, Dec 11, 2019 at 11:45:57AM -0600, Dale wrote

> I don't know how openrdate works but for chrony, set up the config file
> and then /etc/init.d/chronyd start.  After a bit, you can check to see
> how close it is.  If things are working well enough, don't forget to add
> it to a runlevel so that it starts when you boot up. 

  openrdate defaults to set correct time directly, but it does have an
optional parameter to gradually skew local time to the remote time.  I
use openrdate in client mode once a month or so to sync a machine.

--
Walter Dnes <[hidden email]>
I don't run "desktop environments"; I run useful applications

Reply | Threaded
Open this post in threaded view
|

Re: [SOLVED] What ntp/sntp client do people use?

Dale-46
Walter Dnes wrote:

> On Wed, Dec 11, 2019 at 08:37:10PM +1100, Adam Carter wrote
>> chrony on the "server" to sync from the Internet and systemd-timesyncd
>> on the others to sync from the server.
>   Sounds like something Lennart came up with.
>
> On Wed, Dec 11, 2019 at 11:45:57AM -0600, Dale wrote
>
>> I don't know how openrdate works but for chrony, set up the config file
>> and then /etc/init.d/chronyd start.  After a bit, you can check to see
>> how close it is.  If things are working well enough, don't forget to add
>> it to a runlevel so that it starts when you boot up. 
>   openrdate defaults to set correct time directly, but it does have an
> optional parameter to gradually skew local time to the remote time.  I
> use openrdate in client mode once a month or so to sync a machine.
>

Well, if you use chrony as a service, you shouldn't have to do that
anymore.  Each time you boot it will sync up the clocks and it will keep
the clock accurate from then on.  I don't have a laptop but from what
I've read, it even works well on those even tho they may not always be
able to sync due to not always having a internet connection. Give it a
little time, maybe chrony will "grow" on you.  lol 

I updated my chrony config file to this:


server  64.6.144.6
server  209.114.111.1
server  130.207.244.240

server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org
server 3.us.pool.ntp.org


I now get this from chrony:


root@fireball / # chronyc sources -v
210 Number of sources = 7

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current synced, '+' = combined , '-' = not
combined,
| /   '?' = unreachable, 'x' = time may be in error, '~' = time too
variable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted
offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured
offset,
||                                \     |          |  zzzz = estimated
error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last
sample              
===============================================================================
^- triangle.kansas.net           2   7   377    61  +3945us[+4033us]
+/-  113ms
^+ bindcat.fhsu.edu              2   7   377    61  -2796us[-2708us]
+/-   61ms
^* navobs1.gatech.edu            1   7   377    59  -3297us[-3209us]
+/-   21ms
^+ li924-200.members.linode>     2   7   377    60  -4993us[-4905us]
+/-   28ms
^- 208.67.75.242                 2   7   377   128  -1448us[-1362us]
+/-   83ms
^+ 162.159.200.123               3   7   377   127    +13ms[  +13ms]
+/-   36ms
^- srcf-ntp.stanford.edu         2   7   377   128  -1876us[-1791us]
+/-   58ms
root@fireball / #


If I average those, my clock is accurate to about 57ms.  Given I'm not
doing anything that requires a perfect clock, that's close enough.  Can
a person blink that fast???  lol  I might add, either you don't mind
your system being off a bit or your rig has a good built in clock.  I
remember my old rig having a clock that was always drifting bad. 
Sometimes fast, sometimes slow.  I think the temps affected it.  I've
always had a clock tool set my clock.  I don't even know how close the
clock will stay on this machine.  I've never tested it.

Dale

:-)  :-) 

12