On Fri, 11 Nov 2016 17:48:45 -0300, Dererk wrote:
> Usually from the standpoint of some servers that contain timestamp
> operations embedded on them, like databases or things alike, enabling
> -s could possible trigger data corruption, since from one instant to
> the other time change backwards. Th
On 24/05/16 10:09, Antoine Beaupré wrote:
> Package: openntpd
> Version: 1:5.7p4-2~bpo80+1
> Followup-For: Bug #697643
>
> It seems that the -s flag fixes this bug, so either the bug should be
> closed, or -s should be made the default.
>
> It is unclear to me why that is not made the default, coul
Package: openntpd
Followup-For: Bug #697643
Ah and for the record, the default NTP daemon is started with -g in
Debian by default, which is the equivalent of -s in openntpd:
https://manpages.debian.org/cgi-bin/man.cgi?query=ntpd&apropos=0&sektion=0&manpath=Debian+6.0.10+squeeze&format=html&locale
Package: openntpd
Version: 1:5.7p4-2~bpo80+1
Followup-For: Bug #697643
It seems that the -s flag fixes this bug, so either the bug should be
closed, or -s should be made the default.
It is unclear to me why that is not made the default, could this be clarified?
-- System Information:
Debian Rele
Package: openntpd
Followup-For: Bug #697643
Dear Maintainer,
I'm running a new installation of the latest debian stable for powerpc.
the computer had been switched off for quite some time, so it had not the
faintest idea of the fact we do not live in 1970!
I am used (on other systems) to startin
Package: openntpd
Version: 20080406p-4
Severity: normal
Starting Openntpd with a large delta to the real time causes glibc adjtime to
return with an error. I get these log messages:
ntpd[6071]: adjusting local clock by 201060.984298s
ntpd[6071]: adjtime failed: Invalid argument
Apparently adjtim
6 matches
Mail list logo
