tag 701783 unreproducible moreinfo thanks > Dear Maintainer, > > * running ifdown on an interface stopped the ntp service and forced the > clock with ntpdate > * NTP was already running on the system, and it's clock was synced within > expectations > * Clock was forced backwards, which could've lead to data loss for > sensitive applications. > * Network services to be restored (...) > The ntpdate script portion of this stops a running and functional ntp service > and forcibly sets > the date backwards, which is not expected during normal operations.
I'm not sure what is the "ntpdate script portion" you are talking about. None of the scripts in ifupdown-extra runs ntpdate, nor it interacts with the clock in anyway. Could you please describe in more detail which of ifupdown-extra's scripts (/etc/network/if-up.d/00check-network-cable, /etc/network/if-up.d/10check-duplicate-ip, /etc/network/if-up.d/20static-routes or /etc/network/if-up.d/30check-gateway) do you believe responsible for this problem? I'm tagging this as unreproducible + moreinfo because I do not see how ifupdown-extra could have caused the problem you describe. Best regards Javier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
