Your message dated Sat, 2 Apr 2016 18:43:06 +0200
with message-id <20160402164305.GA13147@lamella>
and subject line offline user says goodbye to raw IP addresses!
has caused the Debian Bug report #268289,
regarding offline user says goodbye to raw IP addresses!
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
268289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=268289
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 1.20-5
Severity: normal
File: /usr/share/info/chrony.info.gz
Gentlemen, I have evolved a new way to use chrony. The problem is if
the hardwired IP addresses one puts in chrony.conf ever get stale, as
they will surely do, one will not have one's time corrected, and has no
way of noticing what is going on until one day he notices the beep on
the radio is quite a ways away from his computer time. Even then it
is tough to know exactly what is the problem. Now that I have driven
out the last hardwired IP address from my computer, I will not go
barking up wrong trees when things break. It turns out that the
cards are stacked against the offline chrony user who wishes to banish
raw IP addresses, but I have nonetheless!
What I do is I restart chronyd in /etc/ppp/ip-up.d/chrony, so as an
offline user, I can still use hostnames, and not raw IP addresses.
No, not elegant, but works.
========= Here are some extra grumbles I noted along the way to my solution:
Subject: chrony.info.gz: must use raw IP addresses if offline
In Info,
The `server' directive is immediately followed by either the name of
the server, or its IP address in dotted-quad notation. The server
command also supports a number of subfields (which may be defined in any
order):
Please add right there: if you want to use a name instead of an IP
address, then you had better be online when the chrony daemon is
started (which rules out offline users.)
Therefore we are constantly hounding down IP addresses to amend our
chrony.conf.
Some of us use pdnsd, so chrony calling the DNS shouldn't be too bad,
if the IP happens to be cached.
I wish there was a keyword to "get IP at daemon startup or upon
connection, no big deal to me".
Trying auto_offline: same problem!
OK, now I'll try adding to /etc/ppp/ip-up.d/chrony:
invoke-rc.d chrony restart #jidanni, so our illegal IP's become legal
---worked.
----
Also mention any drawbacks to putting too many servers into chrony.conf.
-----
if one's server's IP addresses change, the typical scenario is weeks
without clock updates, then messages to newsgroups about software
quality :=)
A solution would be a keyword in chrony.conf that could be set to send
mail to root etc. when typical signs of IP addresses that are no
longer valid occur.
================
Anyway, my /etc/ppp/ip-up.d/chrony now looks like
{
/bin/pidof chronyd > /dev/null || exit 0
sleep 44 #jidanni, give connection some time to get warmed up?
invoke-rc.d chrony restart #jidanni, so our illegal IP's become legal!
#They might not be legal at offline reboot time, especially if not using pdnsd,
#but they will be legal (resolvable) now.
sleep 15 #give some time for DNS?
KEY=$(awk '$1 ~ /^commandkey$/ { print $2; exit}' /etc/chrony/chrony.conf)
PASSWORD=`awk '$1 ~ /^'$KEY'$/ {print $2; exit}' /etc/chrony/chrony.keys`
/usr/bin/chronyc << EOF
password $PASSWORD
online
EOF
exit 0
#jidanni: at least that final error masking exit 0 doesn't seem justified.
}& #jidanni, do in background so don't delay other ip-up.d jobs
#I'm not sure any or all the sleeps above are actually needed
#Odd how the Debian guy uses $() on one line and `` on the other.
Anyway, now I can get time updates again! Yes, this isn't exactly how
the chrony author pictured users using the program, but it is the way
I found I can best use it. Worked for over a week already.
--- End Message ---
--- Begin Message ---
Version: 1.26-1
Hello,
This issue should be irrelevant since the 1.25 upstream release.
Starting from this version, chronyd will keep trying to resolve the
hostname specified in the server and peer directives in increasing
intervals until it succeeds. Consequently, I’m closing this bug report.
Cheers,
Vincent
signature.asc
Description: PGP signature
--- End Message ---
