On 2/17/22, Tim Woodall wrote:
>>> It's on my todo list, along with ntp, to move to something else...
>>
>> I've seen references to chrony and ntpsec as replacements.
>
> ntpsec is supposed to be an almost drop in replacement.
If I'm interpreting the popcon pages right,
ntpsec 228 users
chron
On Wed, 16 Feb 2022, Lee wrote:
On 2/12/22, Tim Woodall wrote:
On Wed, 9 Feb 2022, Lee wrote:
Any idea what the chances are of getting an enhancement request for
the dhcp client to add an
ignore option;
that says not use the option given by the dhcp server?
isc-dhcp-client? zero.
https:/
On 2/12/22, Tim Woodall wrote:
> On Wed, 9 Feb 2022, Lee wrote:
>
>> Any idea what the chances are of getting an enhancement request for
>> the dhcp client to add an
>> ignore option;
>> that says not use the option given by the dhcp server?
>>
> isc-dhcp-client? zero.
>
> https://www.isc.org/dhc
On Wed, 9 Feb 2022, Lee wrote:
Any idea what the chances are of getting an enhancement request for
the dhcp client to add an
ignore option;
that says not use the option given by the dhcp server?
isc-dhcp-client? zero.
https://www.isc.org/dhcp/
The client and relay portions of ISC DHCP are n
On Wed, Feb 09, 2022 at 11:00:14AM -0500, Lee wrote:
> *sigh* naturally I picked the "move it somewhere else" option that
> won't prevent an upgrade from re-creating the file.
Missing config files will not be reinstalled, unless you call dpkg
with the "--force-confmiss" option. You should be fine
u know which NTP servers you want this host to use, do you?
> >> >> I tried changing /etc/dhcp/dhclient.conf to request just
> >> >> request subnet-mask, broadcast-address, routers,
> >> >> interface-mtu,
> >> >>
On Wed, Feb 09, 2022 at 11:00:14AM -0500, Lee wrote:
> Any idea what the chances are of getting an enhancement request for
> the dhcp client to add an
> ignore option;
> that says not use the option given by the dhcp server?
apt install dhcpcd5
It can do this, it is called "nooption ntp_servers
:
>> > >> How to tell systemd to leave the ntpd config alone?
>> > >
>> > > What makes you think the two are connected in any way?
>> >
>> > $ grep "Network Time Service" syslog
>> > Feb 6 12:06:48 spot systemd[1]: Stopping
On 2/9/22, Reco wrote:
> Hi.
>
> On Wed, Feb 09, 2022 at 09:05:51AM -0500, Lee wrote:
>> On 2/8/22, Greg Wooledge wrote:
>> > On Tue, Feb 08, 2022 at 02:43:02PM -0500, Lee wrote:
>> >> How to tell systemd to leave the ntpd config alone?
>> >
&g
On Wed, Feb 09, 2022 at 05:44:25PM +0300, Reco wrote:
> Hi.
>
> On Wed, Feb 09, 2022 at 09:05:51AM -0500, Lee wrote:
> > On 2/8/22, Greg Wooledge wrote:
> > > On Tue, Feb 08, 2022 at 02:43:02PM -0500, Lee wrote:
> > >> How to tell systemd to leave the
On Wed, 9 Feb 2022 09:05:51 -0500
Lee wrote:
> 2nd thought was telling the DHCP server to not hand out an NTP server
> address to this one machine, but that's another damnifi know how to.
If you are running isc-dhcp-server, look for "option ntp-servers" in
/etc/dhcp/dhcpd.conf.
Another way to d
Hi.
On Wed, Feb 09, 2022 at 09:05:51AM -0500, Lee wrote:
> On 2/8/22, Greg Wooledge wrote:
> > On Tue, Feb 08, 2022 at 02:43:02PM -0500, Lee wrote:
> >> How to tell systemd to leave the ntpd config alone?
> >
> > What makes you think the two are connected in
On 2/8/22, Greg Wooledge wrote:
> On Tue, Feb 08, 2022 at 02:43:02PM -0500, Lee wrote:
>> How to tell systemd to leave the ntpd config alone?
>
> What makes you think the two are connected in any way?
$ grep "Network Time Service" syslog
Feb 6 12:06:48 spot systemd[
On Tue, Feb 08, 2022 at 02:43:02PM -0500, Lee wrote:
> How to tell systemd to leave the ntpd config alone?
What makes you think the two are connected in any way?
Under bullseye, if the ntp package (which supplies the ntpd program) is
installed, then systemd-timesyncd is removed. The
How to tell systemd to leave the ntpd config alone?
I had everything working with a static ethernet config and then
decided I wanted a media server for my ROKU. My understanding is the
DLNA server has to be on the same subnet as the ROKU, so I joined my
PC to the wlan ... and broke the ntpd
Hello there,
debian is the best - when it works :-) Maybe someone of you will have an
idea. I've run into an issue with time synchronisation on windows 7
clients in a samba 4 ad domain. Setup is as follows:
Server is running debian jessie with samba 4 as PDC and NTPd. I followed
the tut
Good to know.
I was going to suggest that maybe your Internet connection was failing,
but I did not do so because you checked it with another machine.
On 17/08/17 11:04, Kynn Jones wrote:
> It appears that the problem was a network misconfiguration (outside of my
> control), and it is now resolve
Dear sir, unfortunately I do not have a solution to your problem, but I
want to note that in “Failed to start ntpd.service: Unit nptd.service
not found.” the name of ntpd was spelled “nptd”; maybe that is the
source of the problem.
It does not appear to me that ntp is preventing the network from
settings for this are in /etc/systemd/timesyncd.conf.
On Thu, 17 Aug 2017,
Kynn Jones wrote:
Date: Thu, 17 Aug 2017 10:51:15
From: Kynn Jones
To: Debian User
Subject: How to get around ntpd catch-22?
Resent-Date: Thu, 17 Aug 2017 14:51:44 + (UTC)
Resent-From: debian-user
get around ntpd catch-22?
Resent-Date: Thu, 17 Aug 2017 14:51:44 + (UTC)
Resent-From: debian-user@lists.debian.org
I installed Debian on a (legacy) Optiplex 9010 desktop, using a minimal USB
installation image, and netinst. IOW, most of the contents of this
installation came in through the
It appears that the problem was a network misconfiguration (outside of my
control), and it is now resolved.
Sorry for the confusing query.
On Thu, Aug 17, 2017 at 10:00:48AM -0500, Mario Castelán Castro wrote:
> Dear sir, unfortunately I do not have a solution to your problem, but I
> want to note that in “Failed to start ntpd.service: Unit nptd.service
> not found.” the name of ntpd was spelled “nptd”; maybe that is the
&g
ately after.
One can see that the restart of the network is failing due to an ntpd
problem.
If I attempt to restart ntpd, I get the error "Failed to start
ntpd.service: Unit nptd.service not found."
This makes no sense to me: ntpd was clearly available and working for
several hours bef
On Tue, Jan 20, 2015 at 07:39:22AM -0500, R. Clayton wrote:
> I'm on this
>
[cut]
>
> server 0.debian.pool.ntp.org iburst
> server 1.debian.pool.ntp.org iburst
> server 2.debian.pool.ntp.org iburst
> server 3.debian.pool.ntp.org iburst
>
[cut]
>
> this happens
>
> $ ntpq -p
>
R. Clayton:
>
> Why aren't any specified servers in use?
> Why the unspecified clock.monmouth server listed?
Does the machine configure its network using DHCP? Does it receive this
NTP server from the DHCP server with option 42?
http://support.ntp.org/bin/view/Support/ConfiguringNTP#Section_6.12
packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 6.190/6.190/6.190/0.000 ms
$
but when I do this
$ sudo /etc/init.d/ntp restart
[ ok ] Stopping NTP server: ntpd.
[ ok ] Starting NTP server: ntpd.
$ sudo tail -11 /var/log/daemon.log
Jan 20 07:28:
a single new “server” line directing ntpd to
use the DHCP provided server.
When the ntp init.d script runs, it checks to see if there is a
/var/lib/ntp/ntp.conf.dhcp file, and uses it in place of the conventional
/etc/ntp.conf.
The result is what you saw.
If you don’t like that behavior, t
mad wrote:
> I found it. It was DHCP. The NTP init scripts checks if there is a file
> /var/lib/ntp/ntp.conf.dhcp in which the local router is configured as
> only ntp source.
Thank you for posting the resolution of the problem!
Bob
signature.asc
Description: Digital signature
tions not on my home network, with the
>> same configuration show as expected four clock sources. Even starting
>> ntpd on the command line doesn't show any more data and ntpd is compiled
>> without debugging. Probably that is what I will do, recompile ntpd with
>> d
On Mon, Nov 24, 2014 at 10:58:29AM +0100, mad wrote:
> mentioned, other Debian installations not on my home network, with the
> same configuration show as expected four clock sources. Even starting
> ntpd on the command line doesn't show any more data and ntpd is compiled
>
able server shows in "ntpq -p" output.
That is my problem! Not on my internal home network systems. As
mentioned, other Debian installations not on my home network, with the
same configuration show as expected four clock sources. Even starting
ntpd on the command line doesn't show
On Sat, Nov 22, 2014 at 09:57:50PM +0100, mad wrote:
> # ntpq -p
> remote refidst t when poll reach delay offset jitter
>
> fritz.box X.Y.Z.A 3 u- 6411.8740.153 0.052
>
> I use th
e something to do with IPv4 and IPv6. If I
> start ntpd with '-4 -n' ntpq exists with 'Connection refused'. If I
> start it with '-6 -n' ntpq says 'No association ID's returned'.
>
> I'm thoroughly confused.
>
> Does anyone
; "directly on the internet" use all four clock sources
>> (0.debian.pool, 1.debian.pool...).
>>
>> Why is that? It seems to have something to do with IPv4 and IPv6. If I
>> start ntpd with '-4 -n' ntpq exists with 'Connection refused'. If I
>
..).
>
> Why is that? It seems to have something to do with IPv4 and IPv6. If I
> start ntpd with '-4 -n' ntpq exists with 'Connection refused'. If I
> start it with '-6 -n' ntpq says 'No association ID's returned'.
>
> I'm thoroug
6411.8740.153 0.052
I use the default ntp configuration and other Debian installations
"directly on the internet" use all four clock sources
(0.debian.pool, 1.debian.pool...).
Why is that? It seems to have something to do with IPv4 and IPv6. If I
start ntpd with
Mauro writes:
> Here is ntp.conf
>
> statsdir /var/log/ntpstats/
Hm, mine's almost the same, except that I have statistics generation
turned off and am using different servers. Did you try the program I
wrote?
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
On 26 September 2012 15:57, lee wrote:
>
> What's in the configuration of your NTP daemon? Perhaps there's
> something wrong with that.
Here is ntp.conf
statsdir /var/log/ntpstats/
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file
Mauro writes:
> PROBLEM!!
> System clock is gone one hour ahead, ntp stops to run with no messages
> logs and I now I'm in trouble because I don't know what to do.
Try the program below and see what it says. If it actually tells you
that the time is out of sync, you can write a script aroun
September 2012 22:20, Mauro wrote:
>> >>> On 20 September 2012 16:56, John Hasler wrote:
>> >>>> Someone who Stefan failed to identify wrote:
>> >>>>> ...ntpd crashes on my server. Time jumps forward one hour every time
>> >>>>
here should one look?
The final outcome was that -- some years later -- the "-g" option was
added to ntpd. Quoting from "man 8 ntpd":
-g Normally, ntpd exits with a message to the system log if
the offset exceeds the panic threshold, which is 1000 s by
default
-again-part-4-and-last
> >> >
> >> > You can try the mentioned work-around and see if that works for you.
> >> >
> >> > Anyway, if that's the case, you should experience the same with different
> >> > ntp daemons and not just with ntpd :
nd it a bit radical measure for dealing with a problem.
Should we also evaluate a kernel error in that way, no system would be up
for more than... a week? :-)
Either way, ntpd provides some options to conciliate with severely skewed
time which can help to prevent (or mitigate) the daemon t
On 12Sep23:0208-0700, Rick Thomas wrote:
>
> On Sep 22, 2012, at 6:51 AM, Camaleón wrote:
>
> >Anyway, no NTP daemon should crash because of skewed time;
> >one thing is that it refushes to sync (which can be fine,
> >and should log this fact so the admin can make the proper
> >measures) but a di
On Sun, 23 Sep 2012, Neal Murphy wrote:
> I must agree that that was a somewhat braindead decision. 'Failure by design'
> is never an valid option.
>
> If a problem is important enough to require an admin's attention, a daemon
> should demand it via the console and the system logs. Nag repeatedl
On Sunday, September 23, 2012 05:08:19 AM Rick Thomas wrote:
> On Sep 22, 2012, at 6:51 AM, Camaleón wrote:
> > Anyway, no NTP daemon should crash because of skewed time; one thing
> > is
> > that it refushes to sync (which can be fine, and should log this fact
> > so the admin can make the proper
On Sep 22, 2012, at 6:51 AM, Camaleón wrote:
Anyway, no NTP daemon should crash because of skewed time; one thing
is
that it refushes to sync (which can be fine, and should log this fact
so the admin can make the proper measures) but a different thing is
completely killing the service.
Hi
hn Hasler wrote:
> >>>> Someone who Stefan failed to identify wrote:
> >>>>> ...ntpd crashes on my server. Time jumps forward one hour every time
> >>>>> this has happened.
> >>>>
> >>>> I doubt ntpd is crashing. Mo
On Fri, 21 Sep 2012 12:05:01 +0200, Mauro wrote:
> On 20 September 2012 22:20, Mauro wrote:
>> On 20 September 2012 16:56, John Hasler wrote:
>>> Someone who Stefan failed to identify wrote:
>>>> ...ntpd crashes on my server. Time jumps forward one hour eve
On 20 September 2012 22:20, Mauro wrote:
> On 20 September 2012 16:56, John Hasler wrote:
>> Someone who Stefan failed to identify wrote:
>>> ...ntpd crashes on my server. Time jumps forward one hour every time
>>> this has happened.
>>
>> I doubt ntpd i
On 20 September 2012 16:56, John Hasler wrote:
> Someone who Stefan failed to identify wrote:
>> ...ntpd crashes on my server. Time jumps forward one hour every time
>> this has happened.
>
> I doubt ntpd is crashing. Most likely something else is jumping the
> system cl
Someone who Stefan failed to identify wrote:
> ...ntpd crashes on my server. Time jumps forward one hour every time
> this has happened.
I doubt ntpd is crashing. Most likely something else is jumping the
system clock and ntpd is behaving as designed and exiting when it sees a
one hour
>>> with ntpd crashes on my server. Time jumps forward one hour every time
>>> this has happened. However I'm not convinced it's the hardware causing
>> Sounds like something is causing the one-hour jump, and that in turns
>> causes ntpd to go bonkers.
On 18 September 2012 15:51, Stefan Monnier wrote:
>> with ntpd crashes on my server. Time jumps forward one hour every time
>> this has happened. However I'm not convinced it's the hardware causing
>
> Sounds like something is causing the one-hour jump, and that
> with ntpd crashes on my server. Time jumps forward one hour every time
> this has happened. However I'm not convinced it's the hardware causing
Sounds like something is causing the one-hour jump, and that in turns
causes ntpd to go bonkers.
As for what causes this jump, I d
On 17 September 2012 21:47, Bob Proulx wrote:
> Mauro wrote:
>> I think ntpd crashes are because my server lost time.
>> I have ntpd in two server, now I've seen that in one of these ntp
>> crashes and the time of the server is 1 hour forward.
>> That's why
On 17 September 2012 19:33, Gerald Turner wrote:
> Mauro writes:
>> I think ntpd crashes are because my server lost time.
>> I have ntpd in two server, now I've seen that in one of these ntp
>> crashes and the time of the server is 1 hour forward.
>> That'
Mauro wrote:
> I think ntpd crashes are because my server lost time.
> I have ntpd in two server, now I've seen that in one of these ntp
> crashes and the time of the server is 1 hour forward.
> That's why ntp crashes: server time goes 1 hour forward and ntp can't
&g
Mauro writes:
> I think ntpd crashes are because my server lost time.
> I have ntpd in two server, now I've seen that in one of these ntp
> crashes and the time of the server is 1 hour forward.
> That's why ntp crashes: server time goes 1 hour forward and ntp can't
&g
On 16 September 2012 17:46, Camaleón wrote:
> Try by appending the "-x" argument at the "/etc/default/ntp" file from
> the server that crashes. If your thoughs are correct, this could mitigate
> the time difference.
I've uninstalled ntp and installed openntp from squeeze backports.
I hope this w
El 2012-09-16 a las 00:17 +0200, Mauro escribió:
(resending to the list)
> On 15 September 2012 16:47, Camaleón wrote:
> > On Sat, 15 Sep 2012 15:43:04 +0200, Mauro wrote:
> >
> >> I think ntpd crashes are because my server lost time.
> >
> > How can tha
On Sat, 15 Sep 2012 15:43:04 +0200, Mauro wrote:
> I think ntpd crashes are because my server lost time.
How can that be? If ntpd daemon is running, the server has to be synced
and showing the right time. And in the event the time is too much skewed,
ntpd shouldn't crash but left
I think ntpd crashes are because my server lost time.
I have ntpd in two server, now I've seen that in one of these ntp
crashes and the time of the server is 1 hour forward.
That's why ntp crashes: server time goes 1 hour forward and ntp can't
resynchronize so it crashes.
Now I do
Mauro wrote:
> What's the difference of running ntpdate instead ntp with cron?
'ntpdate' jumps the clock. It was intended for use at system boot
time when that is okay to do. 'ntpd' is a daemon that runs and makes
small clock adjustments as needed to keep tim
On Tue, 11 Sep 2012 22:54:50 +0200, Mauro wrote:
> On 11 September 2012 17:32, Camaleón wrote:
(...)
>>>> You can try a different approach: do not run ntpd as daemon but using
>>>> cron and see how it goes :-?
>>>
>>> What's the difference of
On Tue, 11 Sep 2012 17:16:05 +0100, Chris Davies wrote:
> Camaleón wrote:
>> You can try a different approach: do not run ntpd as daemon but using
>> cron and see how it goes :-?
>
> Huh?
Yes, for testing purposes.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, emai
; though, you need to be aware that ntpdate is quite likely to jump the
>>>>> clock.
>>>>
>>>> If ntp stops running with apparently no reasons I don't know what else
>>>> I can do. I need to have time synchronized between my servers.
>>
Camaleón wrote:
> You can try a different approach: do not run ntpd as daemon but using
> cron and see how it goes :-?
Huh?
Chris
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o
Ralf Mardorf wrote:
> Does "jump the clock" mean that the time is synced hard, ignoring
> timestamps?
Yes.
Ntpdate is as likely to set the clock back as it is to put it
forward. Your applications might be able to cope with a second being
only 800ms long, but databases and the like get very upset
t;>>
>>> If ntp stops running with apparently no reasons I don't know what else
>>> I can do. I need to have time synchronized between my servers.
>>
>> You can try a different approach: do not run ntpd as daemon but using
>> cron and see how it goes :-
On 11 September 2012 13:03, Ralf Mardorf wrote:
> On Tue, 2012-09-11 at 12:54 +0200, Mauro wrote:
>> On 11 September 2012 10:58, Chris Davies wrote:
>> > Mauro wrote:
>> >> I think the best solution is uninstall ntp and use ntpdate with cron.
>> >
>> > Not a particularly good solution for a numb
eed to have time synchronized between my servers.
>
> You can try a different approach: do not run ntpd as daemon but using
> cron and see how it goes :-?
What's the difference of running ntpdate instead ntp with cron?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
,
>> though, you need to be aware that ntpdate is quite likely to jump the
>> clock.
>
> If ntp stops running with apparently no reasons I don't know what else I
> can do. I need to have time synchronized between my servers.
You can try a different approach: do
On Tue, 2012-09-11 at 12:54 +0200, Mauro wrote:
> On 11 September 2012 10:58, Chris Davies wrote:
> > Mauro wrote:
> >> I think the best solution is uninstall ntp and use ntpdate with cron.
> >
> > Not a particularly good solution for a number of reasons. Mainly, though,
> > you need to be aware
On 11 September 2012 10:58, Chris Davies wrote:
> Mauro wrote:
>> I think the best solution is uninstall ntp and use ntpdate with cron.
>
> Not a particularly good solution for a number of reasons. Mainly, though,
> you need to be aware that ntpdate is quite likely to jump the clock.
If ntp stop
Mauro wrote:
> I think the best solution is uninstall ntp and use ntpdate with cron.
Not a particularly good solution for a number of reasons. Mainly, though,
you need to be aware that ntpdate is quite likely to jump the clock.
Chris
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debia
On 11 September 2012 00:08, Gerald Turner wrote:
> Camaleón writes:
>
>> On Sat, 08 Sep 2012 13:31:16 +0200, Mauro wrote:
>>
>>> Hello I've two server with debian squeeze and in cluster with
>>> heartbeat+pacemaker.
>>> They run ntpd for time
Camaleón writes:
> On Sat, 08 Sep 2012 13:31:16 +0200, Mauro wrote:
>
>> Hello I've two server with debian squeeze and in cluster with
>> heartbeat+pacemaker.
>> They run ntpd for time synchronize.
>> I've noticed some ntpd crashes in random days and rando
El 2012-09-09 a las 22:20 +0200, Mauro escribió:
(resending to the list)
> On 9 September 2012 19:52, Camaleón wrote:
> > On Sat, 08 Sep 2012 13:31:16 +0200, Mauro wrote:
> >
> >> Hello I've two server with debian squeeze and in cluster with
> >> heartbeat+
On Sat, 08 Sep 2012 13:31:16 +0200, Mauro wrote:
> Hello I've two server with debian squeeze and in cluster with
> heartbeat+pacemaker.
> They run ntpd for time synchronize.
> I've noticed some ntpd crashes in random days and random hour.
Does restarting the service works?
Hi Bob.
On Sunday, 01 March 2009 16:13:25 +,
Bob Cox wrote:
> > After to have updated to Debian GNU/Linux Lenny (stable), I began to
> > see abundantly /var/log/ntpd entries of the following type:
> >
> > 1 Mar 06:50:52 ntpd[4825] kernel time sync status change
On Sun, Mar 01, 2009 at 11:33:05 -0200, Daniel Bareiro (daniel-lis...@gmx.net)
wrote:
> Hi all!
>
> After to have updated to Debian GNU/Linux Lenny (stable), I began to see
> abundantly /var/log/ntpd entries of the following type:
>
> 1 Mar 06:50:52 ntpd[4825] kernel time
Hi all!
After to have updated to Debian GNU/Linux Lenny (stable), I began to see
abundantly /var/log/ntpd entries of the following type:
1 Mar 06:50:52 ntpd[4825] kernel time sync status change 4001
1 Mar 07:42:06 ntpd[4825] kernel time sync status change 0001
1 Mar 09:24:29 ntpd[4825] kernel
On Monday 16 June 2008 22:08, David Christensen wrote:
> Andrew Reid wrote:
> > I'm afraid I'm not much of an expert on openntp. My first guess is
> > that, as the system runs, the clock should sync up on its own, if
> > ntpd is seeing valid servers and working prop
Andrew Reid wrote:
> I'm afraid I'm not much of an expert on openntp. My first guess is
> that, as the system runs, the clock should sync up on its own, if
> ntpd is seeing valid servers and working properly.
If it were a 24x7 box, then yes. But, it's a virtual mach
On Sunday 15 June 2008 17:10, David Christensen wrote:
> Andrew Reid wrote:
> > Check if there is also an /etc/init.d/ntpd. If your box used
> > to have ntp, and that package was removed but not purged, the init
> > files will still be in place. /etc/init.d/ntpd will
Andrew Reid wrote:
> Check if there is also an /etc/init.d/ntpd. If your box used
> to have ntp, and that package was removed but not purged, the init
> files will still be in place. /etc/init.d/ntpd will find
> the openntp executable and try to run it, but with wierd/wrong
> op
penntpd, /etc/default/openntpd, etc., but
> couldn't figure out if or where a -p option was being set (although I did
> set the -s option).
> Any suggestions?
Check if there is also an /etc/init.d/ntpd. If your box used
to have ntp, and that package was removed but not purged, th
:
3.9p1-3 - time-daemon
Reverse Provides:
When I boot, I see the following message on the console:
Starting NTP server: ntpd/usr/sbin/ntpd: invalid option -- p
usage: ntpd [-dSs] [-f file]
failed!
But, ntpd seems to be running (?):
20080615-103358 [EMAIL PROTECTED] ~/vd40r0
# ps -A | grep ntp
gt;
> >I wonder if it's possible to persuade the dhcp client to run a script?
>
> Sorry to resurrect such an old thread but this is really irritating me,
> after reading through the Bug Reports it seems this has been fixed in
> version 4.2.4 which is fine for Lenny but I do
etch box with nothing other than
> main and updates in its /etc/apt/sources.list so I don't want to start
> messing around with apt pinning.
>
> Is there a simple way to get the dhcp client to restart ntpd on IP
> address change?
>
> Thank you.
>
> http://b
.list so I don't want to start
messing around with apt pinning.
Is there a simple way to get the dhcp client to restart ntpd on IP
address change?
Thank you.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455717
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439734
http://bugs.debian.org
Cameron Hutchison wrote:
Bob wrote:
Bob wrote:
Is there such a thing?
When my firewall / dhcp server / ntp server gets a fresh IP address
from my ISP the ntp daemon stops responding to requests.
Is the silence because it's a stupid question or because there isn't a
preferred
Bob wrote:
>Bob wrote:
>> Is there such a thing?
>>
>> When my firewall / dhcp server / ntp server gets a fresh IP address
>> from my ISP the ntp daemon stops responding to requests.
>>
>Is the silence because it's a stupid question or because there isn't a
>preferred work around for this?
How d
Bob wrote:
Is there such a thing?
When my firewall / dhcp server / ntp server gets a fresh IP address
from my ISP the ntp daemon stops responding to requests.
This is a well know bug [0] and there are a lot of posts about it but
no consensus on a work around.
Any help?
Thanks
[0] it's so
Is there such a thing?
When my firewall / dhcp server / ntp server gets a fresh IP address from
my ISP the ntp daemon stops responding to requests.
This is a well know bug [0] and there are a lot of posts about it but no
consensus on a work around.
Any help?
Thanks
[0] it's so old a well
On Mon, 2007-01-29 at 12:42 -0800, Peter Easthope wrote:
> gf> You also need to configure your machine that you are referencing to
> reply to requests.
>
> gf> http://www.eecis.udel.edu/~mills/ntp/html/index.html
>
> gf> Usually, you need to allow local only clients/networks.
>
> That is more h
Hello Greg,
gf> You are confusing rdate and ntp.
I understand that they are distinct programs.
gf> rdate (traditionally) does not even speak the protocol of ntp.
I am trying to follow the instructions in 16.4.1 here.
(Join the following two lines.)
http://www.debian.org/doc/manuals/
system
ct: Connection refused
> >
> > I have the ntpd man page and it isn't helping.
> > Someone please give a hint of what is needed
> > in /etc/ntp.conf.
>
> You are confusing rdate and ntp.
>
> rdate is port 37 (tcp and udp), typically disabled as a DoS
On Wed, 2007-01-24 at 10:15 -0800, Easthope wrote:
> ntp is installed on a server here and appears to work.
> Yet another machine runs rdate at startup and produces
> this report.
>
> rdate: connect: Connection refused
>
> I have the ntpd man page and it isn't helpin
1 - 100 of 199 matches
Mail list logo
