Chris Davies wrote, on 01/12/12 00:12:
Jörg-Volker Peetz jvpe...@web.de wrote:
Here I'm using rdate -an in a cron job with something like the following
rdate -acnv $NTPHOST
Just like ntpdate or any of the other cron based solutions proposed in
this thread, this does not train the clock. So
Hi, all:
I see this message when running an update:
Installing new version of config file /etc/cron.daily/ntp ...
insserv: warning: current stop runlevel(s) (0 1 6) of script `ntp'
overwrites defaults (empty).
Should I be concerned about it? And, if so, what am I supposed to do
to correct it.
Good time of the day, Patrick.
You worte:
I see this message when running an update:
Installing new version of config file /etc/cron.daily/ntp ...
insserv: warning: current stop runlevel(s) (0 1 6) of script `ntp'
overwrites defaults (empty).
Should I be concerned about it? And, if so, what am
Patrick Wiseman wrote:
I see this message when running an update:
Installing new version of config file /etc/cron.daily/ntp ...
insserv: warning: current stop runlevel(s) (0 1 6) of script `ntp'
overwrites defaults (empty).
That is a minor upgrade bug in the ntp package. You had a previous
Sthu Deus wrote:
Not answering to Your question, but as mine opinion - if You do not
intend other hosts to be sync-ing time w/ this host, I think You need
the service at all.
Time is important to most internet hosts. We always hate to see email
from users with a date of 1970 for example. I
On Wed, Jan 11, 2012 at 12:26 PM, Bob Proulx b...@proulx.com wrote:
Patrick Wiseman wrote:
I see this message when running an update:
Installing new version of config file /etc/cron.daily/ntp ...
insserv: warning: current stop runlevel(s) (0 1 6) of script `ntp'
overwrites defaults (empty).
Bob Proulx wrote, on 01/11/12 18:32:
Sthu Deus wrote:
Not answering to Your question, but as mine opinion - if You do not
intend other hosts to be sync-ing time w/ this host, I think You need
the service at all.
Time is important to most internet hosts. We always hate to see email
from
On Mi, 11 ian 12, 10:26:48, Bob Proulx wrote:
For reasons that I haven't been following there has been a push to
remove those shutdown links generally from everything. I don't know
why. Perhaps someone else will comment on why. Removing those links
seems like it breaks going to single
Andrei Popescu wrote:
Bob Proulx wrote:
For reasons that I haven't been following there has been a push to
remove those shutdown links generally from everything. I don't know
why. Perhaps someone else will comment on why. Removing those links
seems like it breaks going to single user
On Mi, 11 ian 12, 15:01:57, Bob Proulx wrote:
From lurking on debian-devel I can tell that your guess is right on :)
(the motive is to speed-up the shutdown).
Is there a plan for packages to deal with the links that are left
behind? Could we, should we, start filing bugs if a package
Jörg-Volker Peetz jvpe...@web.de wrote:
Here I'm using rdate -an in a cron job with something like the following
rdate -acnv $NTPHOST
Just like ntpdate or any of the other cron based solutions proposed in
this thread, this does not train the clock. So although rdate slews the
clock, it doesn't
On Jan 11, 2012, at 10:17 AM, Sthu Deus wrote:
Good time of the day, Patrick.
You worte:
I see this message when running an update:
Installing new version of config file /etc/cron.daily/ntp ...
insserv: warning: current stop runlevel(s) (0 1 6) of script `ntp'
overwrites defaults (empty).
12 matches
Mail list logo
