know how to interpret, gdb -c /ntpd.core. (I
haven't really used gdb before, so if I am not doing something
correctly with it, please feel free to let me know)
Ah, you need to build ntpd with -g in CFLAGS LDFLAGS for debugging
symbols to be present
at the risk of sounding like
I am running NTPD built from ports on system that has had world rebuilt
without ntp. After doing some port updates this morning to the latest
OpenSSL which caused ntp to rebuild as its built against the OpenSSL
port. ntpd now core dumps at start, in order to attempt and resolve the
issue I
On Apr 23, 2012, at 11:13 AM, Dean E. Weimer wrote:
I am running NTPD built from ports on system that has had world rebuilt
without ntp. After doing some port updates this morning to the latest
OpenSSL which caused ntp to rebuild as its built against the OpenSSL port.
ntpd now core dumps
On 23.04.2012 13:19, Chuck Swiger wrote:
On Apr 23, 2012, at 11:13 AM, Dean E. Weimer wrote:
I am running NTPD built from ports on system that has had world
rebuilt without ntp. After doing some port updates this morning to
the latest OpenSSL which caused ntp to rebuild as its built against
if I am not doing something correctly with it, please feel free to
let me know)
Ah, you need to build ntpd with -g in CFLAGS LDFLAGS for debugging symbols to
be present
Regards,
--
-Chuck
___
freebsd-questions@freebsd.org mailing list
http
. (I
haven't really used gdb before, so if I am not doing something
correctly with it, please feel free to let me know)
Ah, you need to build ntpd with -g in CFLAGS LDFLAGS for debugging
symbols to be present
at the risk of sounding like an complete n00b, how do I do that? After
reading
On Feb 5, 2012, at 10:39 PM, Radek Krejča wrote:
I have problem with using ntpd on 8.2 amd64 (not tested elsewhere). If I have
a lot of interfaces (vlans) ntpd crashes with segmentation fault (core dump).
I have tested on my test machine and it really depends on number of
interfaces. It try
Hello,
I have problem with using ntpd on 8.2 amd64 (not tested elsewhere). If I have a
lot of interfaces (vlans) ntpd crashes with segmentation fault (core dump). I
have tested on my test machine and it really depends on number of interfaces.
It try to bind on every of it.
I want to reduce
After installing 9.0RC2 I'm getting the following warnings at boot time:
Dec 9 10:31:09 curlew ntpd[1081]: bind() fd 23, family AF_INET6, port 123,
scope 3, addr fe80::6ef0:49ff:fe9e:8897, mcast=0 flags=0x11 fails: Can't
assign
requested address
Dec 9 10:31:09 curlew ntpd[1081]: unable
/localtime is a copy of /usr/share/zoneinfo/Europe/Berlin
and I have set both ntpd_enable=YES and
ntpd_sync_on_start=YES.
ntpd has a sanity check -- if the clock is out by more than 1000
seconds it will give up. So you may have to manually set the clock
to something close to correct before
will be calculated for your timezone whenever you want to display
the time.
ntpd will synch your system clock to UTC, except that on reboot the
systems' initial concept of what time it is comes from the CMOS clock,
possibly offset by a certain number of hours if it thinks the CMOS clock
is using local
On Sat, 12 Feb 2011 11:42:19 +
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
On 11/02/2011 21:16, Christopher J. Ruwe wrote:
Since some weeks my local clock runs two hours early.
My /etc/localtime is a copy of /usr/share/zoneinfo/Europe/Berlin
and I have set both
Since some weeks my local clock runs two hours early. My /etc/localtime
is a copy of /usr/share/zoneinfo/Europe/Berlin and I have set both
ntpd_enable=YES and ntpd_sync_on_start=YES. My ntp.conf consists of
server ntp1.ptb.de prefer
server ntp2.ptb.de
restrict default ignore
restrict 127.0.0.1
On Feb 11, 2011, at 1:16 PM, Christopher J. Ruwe wrote:
My ntp.conf consists of
server ntp1.ptb.de prefer
server ntp2.ptb.de
restrict default ignore
restrict 127.0.0.1
Surely, I must be missing something. Does anybody have an idea?
What does ntpq -p -c rv indicate?
It wouldn't
On Fri, Feb 11, 2011 at 1:16 PM, Christopher J. Ruwe c...@cruwe.de wrote:
Since some weeks my local clock runs two hours early. My /etc/localtime
is a copy of /usr/share/zoneinfo/Europe/Berlin and I have set both
ntpd_enable=YES and ntpd_sync_on_start=YES.
ntpd has a sanity check
ntpd_enable=YES and ntpd_sync_on_start=YES.
ntpd has a sanity check -- if the clock is out by more than 1000
seconds it will give up. So you may have to manually set the clock to
something close to correct before ntpd will handle it. Or pass ntpd
the -g flag to disable the initial sanity check
ntpd_enable=YES and ntpd_sync_on_start=YES.
ntpd has a sanity check -- if the clock is out by more than 1000
seconds it will give up. So you may have to manually set the clock to
something close to correct before ntpd will handle it. Or pass ntpd
the -g flag to disable the initial sanity check
find any definitive instructions as to how to get this working on my
FreeBSD server.
If anyone has this working, or knows of how I can get this configured and
running with ntpd, a little help would be most appreciated...
---
Howard
I've seen reference to this in the man page for astro
.
That said, I have googled and binged and everything else, and I'll be damned
if I can find any definitive instructions as to how to get this working on
my
FreeBSD server.
If anyone has this working, or knows of how I can get this configured and
running with ntpd, a little help would be most
this working on my
FreeBSD server.
If anyone has this working, or knows of how I can get this configured and
running with ntpd, a little help would be most appreciated...
---
Howard
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
Hi.
This is the second time I noted it.
2581 root 1 1180 11736K 3532K CPU66 60.7H 100.00% ntpd
# ntpq -p
localhost: timed out, nothing received
***Request timed out
` /etc/rc.d/ntpd restart` make it work. What can be the reason ?
2581 ntpd CALL select
On 13/09/2010 4:45 PM, Omer Faruk SEN wrote:
Hi,
I am trying to sync my time against a ntp server on Active Directory
but no matter what i do ntpd did not sync against AD's NTP server.
ntpdate works perfectly against AD but not ntpd.
I think you will have trouble doing this. AD's time service
Hi,
I am trying to sync my time against a ntp server on Active Directory
but no matter what i do ntpd did not sync against AD's NTP server.
ntpdate works perfectly against AD but not ntpd.
Here is my ntpd.conf:
restrict default nomodify notrap noquery
restrict 127.0.0.1
server 10.0.0.85
On Mon, 13 Sep 2010 09:45:22 +0300
Omer Faruk SEN omerf...@gmail.com wrote:
restrict default nomodify notrap noquery
restrict 127.0.0.1
server 10.0.0.85 !! Active Directory server (w2k8 r2)
Don't you also need a restrict line for 10.0.0.85?
--
Bruce Cran
from the GUI:
ntpd -g -q
is hanging indefinitely. Logs we've captured do not give any clues. This is the
log from a BSD 7 system:
17 Feb 06:35:36 ntpd[3578]: logging to file /var/log/ntpd.log
17 Feb 06:35:36 ntpd[3578]: ntpd 4.2.0-a Sun Feb 24 09:12:07 UTC 2008 (1)
17 Feb 06:35:36 ntpd[3578
Hi--
On Feb 17, 2010, at 7:24 AM, Peter Steele wrote:
[ ... ]
It never gets past this last log line and we have to do a kill -9 on the ntpd
process. Everything is identical as far as the conf and drift files are
concerned, we're using lagg interfaces on both systems. The versions
8.224 8.168
+217.160.254.116 209.51.161.238 2 u 38 512 37 55.111 -7.128 10.347
+198.247.173.220 128.206.12.130 3 u 39 512 37 47.401 -1.149 3.659
status=c624 sync_alarm, sync_ntp, 2 events, event_peer/strat_chg,
version=ntpd 4.2.0-a Sun Feb 24 09:12:07 UTC 2008 (1
,
version=ntpd 4.2.0-a Sun Feb 24 09:12:07 UTC 2008 (1),
processor=amd64, system=FreeBSD/7.0-RELEASE-p9, leap=11, stratum=16,
precision=-20, rootdelay=0.000, rootdispersion=8.340, peer=25349,
refid=INIT, reftime=. Wed, Feb 6 2036 22:28:16.000,
poll=4, clock=cf26c2d5.ea2b4541
Resending this message. For some reason my post never showed up...
-Original Message-
From: Peter Steele
Sent: Wednesday, February 17, 2010 11:51 AM
To: freebsd-questions@freebsd.org
Subject: RE: What would make ntpd hang in BSD 8?
ntpq -pc rv localhost
cat /etc/ntp.conf
My
Hello,
Jerry pisze:
ntpd_enable=YES
ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift
Assuming you are running the system ntpd file, the above are not
really required. They are the defaults anyway. Try commenting out the
line and restarting ntpd.
Thank you Jerry
On Wed, 29 Jul 2009 08:48:44 +0200
Zbigniew Szalbot z.szal...@lcwords.com wrote:
Hello,
Jerry pisze:
ntpd_enable=YES
ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid
-f /var/db/ntp.drift
Assuming you are running the system ntpd file, the above are not
really required
/ntpd.pid -f /var/db/ntp.drift
Assuming you are running the system ntpd file, the above are not
really required. They are the defaults anyway. Try commenting out the
line and restarting ntpd.
and here's the details of /etc/ntp.conf file:
server 0.pl.pool.ntp.org
server 1.pl.pool.ntp.org
Hello,
I guess there is something simple that is wrong but my server is not
really keeping the correct time. I have these options in /etc/rc.conf
ntpd_enable=YES
ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift
and here's the details of /etc/ntp.conf file:
server
On Jul 27, 2009, at 3:44 PM, Zbigniew Szalbot wrote:
and here's the details of /etc/ntp.conf file:
server 0.pl.pool.ntp.org
server 1.pl.pool.ntp.org
server 2.pl.pool.ntp.org
server 3.pl.pool.ntp.org
driftfile /var/db/ntp.drift
restrict default nopeer nomodify
I used to have server
On Tue, Jul 28, 2009 at 12:44:50AM +0200, Zbigniew Szalbot wrote:
Hello,
I guess there is something simple that is wrong but my server is not
really keeping the correct time. I have these options in /etc/rc.conf
ntpd_enable=YES
ntpd_flags=-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f
Chuck Swiger pisze:
You can't readily combine a restrict statement with using random
timeservers from the NTP pool; you would need to list specific servers
and add blank restrict statements for each server you trust. What
you've configured is likely querying the 4 servers listed for time,
Hi--
On Jul 27, 2009, at 4:08 PM, Zbigniew Szalbot wrote:
OK. So removing the restrictions should cause the time to be synced?
Thank you for your patience and help!
Yes, try it and see-- it's most likely to be the cause of problems.
If you want to set a default restrict line, you'll want
Hi,
Some coarse reading of ntpd(8) and ntp.conf(5) doesn't lead me to believe it's
possible to make ntpd *not* adjust the time. With adjust I don't mean the skew
operation, but really change the time. Backwards is my primary concern but if
it can be turned off completely it's fine with me
Mel Flynn wrote:
Hi,
Some coarse reading of ntpd(8) and ntp.conf(5) doesn't lead me to believe
it's
possible to make ntpd *not* adjust the time. With adjust I don't mean the
skew
operation, but really change the time. Backwards is my primary concern but if
it can be turned off
On Tuesday 21 April 2009 11:39:32 Matthew Seaman wrote:
Mel Flynn wrote:
Hi,
Some coarse reading of ntpd(8) and ntp.conf(5) doesn't lead me to believe
it's possible to make ntpd *not* adjust the time. With adjust I don't
mean the skew operation, but really change the time. Backwards
On Tue, Apr 21, 2009 at 3:39 AM, Matthew Seaman
m.sea...@infracaninophile.co.uk wrote:
Mel Flynn wrote:
Hi,
Some coarse reading of ntpd(8) and ntp.conf(5) doesn't lead me to believe
it's
possible to make ntpd *not* adjust the time. With adjust I don't mean the
skew
operation
On Tue, 21 Apr 2009 14:09:09 +0200
Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote:
On Tuesday 21 April 2009 11:39:32 Matthew Seaman wrote:
* Don't run 'ntpd -g' as the documentation tells you is the
modern and accepted method. Instead, run 'ntpdate' as a separate
process
a date command that
sets time to the past, for example?
ntpdate may be deprecated, but it's been deprecated for years, and I
doubt it will go away until ntpd fully replaces it's functionality.
ntpd -gq can replace ntpdate in a crontab, but ntpd -gqn doesn't really
replace ntpdate -b in the boot
On Tuesday 21 April 2009 16:11:52 Tim Judd wrote:
On Tue, Apr 21, 2009 at 3:39 AM, Matthew Seaman
m.sea...@infracaninophile.co.uk wrote:
Mel Flynn wrote:
Hi,
Some coarse reading of ntpd(8) and ntp.conf(5) doesn't lead me to
believe
it's
possible to make ntpd *not* adjust
that it happens in the background, and after a delay.
Care to expand on that? Dovecot won't stop if root issues a date
command that sets time to the past, for example?
I was assuming that since you're running ntpd you wouldn't be doing
that.
ntpdate may be deprecated, but it's been deprecated for years
Hi, Mel--
On Apr 21, 2009, at 2:06 AM, Mel Flynn wrote:
Some coarse reading of ntpd(8) and ntp.conf(5) doesn't lead me to
believe it's
possible to make ntpd *not* adjust the time. With adjust I don't
mean the skew
operation, but really change the time.
Perhaps I've missed it elsewhere
problem is not the step, but the
fact that it happens in the background, and after a delay.
Care to expand on that? Dovecot won't stop if root issues a date
command that sets time to the past, for example?
I was assuming that since you're running ntpd you wouldn't be doing
that.
Right
On Apr 21, 2009, at 11:23 AM, Mel Flynn wrote:
Now I'm also wondering how ntpd handles securelevel 2.
man init suggests that stepping the clock by more than a second is
disallowed:
2 Highly secure mode - same as secure mode, plus disks may not
be
opened for writing
On Tuesday 21 April 2009 20:29:18 Chuck Swiger wrote:
On Apr 21, 2009, at 11:23 AM, Mel Flynn wrote:
Now I'm also wondering how ntpd handles securelevel 2.
man init suggests that stepping the clock by more than a second is
disallowed:
yes, so does it bail or retry till skew wins over
On Apr 21, 2009, at 11:33 AM, Mel Flynn wrote:
On Tuesday 21 April 2009 20:29:18 Chuck Swiger wrote:
On Apr 21, 2009, at 11:23 AM, Mel Flynn wrote:
Now I'm also wondering how ntpd handles securelevel 2.
man init suggests that stepping the clock by more than a second is
disallowed:
yes, so
On Tuesday 21 April 2009 19:43:30 Chuck Swiger wrote:
Hi, Mel--
On Apr 21, 2009, at 2:06 AM, Mel Flynn wrote:
Some coarse reading of ntpd(8) and ntp.conf(5) doesn't lead me to
believe it's
possible to make ntpd *not* adjust the time. With adjust I don't
mean the skew
operation
On Apr 21, 2009, at 11:57 AM, Mel Flynn wrote:
[ ... -x option... ]
Hmm, that might work. Thanks!
Sure.
It should be surprising that your clock would jump by 6 seconds. Do
you have adequate upstream timesources (ie, at least 4) configured,
is
your local HW clock busted somehow, or are
On Tuesday 21 April 2009 21:07:34 Chuck Swiger wrote:
Try contacting your ISP for nearby NTP
sources,
Anchorage, AK, is special that way. I'll check with ACS if they have one, but
if they don't, even traffic to the local competitor (GCI) goes through
Seattle.
--
Mel
to the past, for example?
I was assuming that since you're running ntpd you wouldn't be doing
that.
Right, then this works because ntpdate is started before dovecot in
rcorder, like Tim Judd said else in thread.
ntpdate and ntpd normally start consecutively, both way before
Dovecot
: don't know how to
make /usr/obj/usr/src/usr.sbin/ntp/ntpd/../libparse/libparse.a. Stop
Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions
install
# /etc/rc.d/named restart
...and I got:
make: don't know how to
make
/usr/obj/usr/src/usr.sbin/ntp/ntpd/../libparse/libparse.a.
Stop
Hi, you can try updating the complete system by using csup(1),
take a look at:
http://www.freebsd.org/doc/en/books/handbook/cvsup.html
I
My ntpd will not sync on my newly installed 7.1-PRERELEASE hosts. The
configuration is the same as other correctly time synched hosts. They
are behind the same firewall. The only difference is that these hosts
are running 7.1.
Does anyone have any tricks for getting ntpd to sync on 7.1
There was recently a thread that I started relating to ntpd not
starting correctly becuase DNS and network were not available at the
time of start. Do a
ps -U root | grep ntpd
If you see 2 processes, then the thread I mention may apply to you.
If you see one or no processes, then that thread
On Fri, 21 Nov 2008 16:47:50 -0800
Nerius Landys [EMAIL PROTECTED] wrote:
I believe that the fix for this is to add a dependency
to /etc/rc.d/ntpd script, adding named to REQUIRE section in
comments. In your opinion, is this a robust fix? For example the
line in my /etc/rc.d/ntpd script
This shouldn't be needed as ntpd already requires ntpdate and in
turn ntpdate requires named. The issue is probably timing - that named
isn't ready.
Actually, the REQUIRE thing in the /etc/rc.d scripts means if the
required service is enabled, start it before this one. It does not
mean start
On Fri, 5 Dec 2008 13:22:29 -0800
Nerius Landys [EMAIL PROTECTED] wrote:
This shouldn't be needed as ntpd already requires ntpdate and in
turn ntpdate requires named. The issue is probably timing - that
named isn't ready.
Actually, the REQUIRE thing in the /etc/rc.d scripts means
understand why enabling ntpdate in
rc.conf fixed my problem of ntpd's DNS resolver child process not
completing (returning). My guess was that NETWORK and named were
guaranteed getting run before ntpd if I included ntpdate in rc.conf.
I thought that perhaps NETWORK and named were not getting run before
ntpd
RW wrote:
On Fri, 21 Nov 2008 16:47:50 -0800
Nerius Landys [EMAIL PROTECTED] wrote:
I believe that the fix for this is to add a dependency
to /etc/rc.d/ntpd script, adding named to REQUIRE section in
comments. In your opinion, is this a robust fix? For example the
line in my /etc/rc.d
On Sat, 06 Dec 2008 01:11:38 +0100
cpghost [EMAIL PROTECTED] wrote:
RW wrote:
I have a similar issue with PPP not having connected by the time
ntpdate runs , so I just have a script that runs between named and
ntpdate, and blocks waiting for access.
Those timing / start-order issues
FreeBSD 7.0. I am having a problem when ntpd starts at bootup. It
continues to have 2 processes running, the process which does the DNS lookup
fails to exit, and ntpd fails to adjust the clock even after days of
running. Immediately after bootup and several hours or days later this is
what
FreeBSD 7.0. I am having a problem when ntpd starts at bootup. It
continues to have 2 processes running, the process which does the DNS lookup
fails to exit, and ntpd fails to adjust the clock even after days of
running. Immediately after bootup and several hours or days later this is
what
I don't know why those processes are hung after boot, but in order to
troubleshoot the problem, I suggest that you modify the /etc/rc.d/ntpd
script to invoke ntpd from truss and log the output to a file, e.g.
/tmp/truss.log.$$. Once you've rebooted, kill the processes and post
the the log
When ntpd first starts up, it forks a child process to perform DNS
resolution of the timeservers listed in its config. If that fails, that
generally indicates that DNS was not working at the time, or something else
was going wrong with the network.
[ See ntpd/ntp_config.c, search for fork
On Dec 3, 2008, at 1:01 PM, Nerius Landys wrote:
[ ... ]
Does anyone know why I'm getting 2 ntpd processes running after bootup
(and ntpd fails to adjust the clock as a result)? Any suggested fix
would be appreciated.
When ntpd first starts up, it forks a child process to perform DNS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nerius Landys wrote:
FreeBSD 7.0. I am having a problem when ntpd starts at bootup. It
continues to have 2 processes running, the process which does the DNS lookup
fails to exit, and ntpd fails to adjust the clock even after days of
running
On Saturday 22 November 2008 01:47:50 Nerius Landys wrote:
Trying to reproduce problem. On a running system. I shut down named. Then
I restart ntpd, then I start named. I can reproduce the problem that
happens on bootup - ntpd has 2 processes and does not adjust the clock.
Restarting ntpd
FreeBSD 7.0. I am having a problem when ntpd starts at bootup. It
continues to have 2 processes running, the process which does the DNS lookup
fails to exit, and ntpd fails to adjust the clock even after days of
running. Immediately after bootup and several hours or days later this is
what I
Hi all,
Ive been toying with setting up my old Garmin GPS12 as a reference for a
server (FreeBSD 6.2) running ntpd, but Ive run into an issue.
Ive searched around a bit and cant find an answer, perhaps because there
isnt one.
Is there any way I can set ntpd to expect a $GPRMC string every 2
On 9/19/08, Tom Storey [EMAIL PROTECTED] wrote:
Hi all,
Ive been toying with setting up my old Garmin GPS12 as a reference for a
server (FreeBSD 6.2) running ntpd, but Ive run into an issue.
Is it possible the issue isn't what you think it is?
Ive searched around a bit and cant find
I'd enable the two furthest apart in the hope that they may
coincide with different seconds, and hopefully ntpd would be able to
work it out from that. I even tried enabling all 3 of them (mode 7),
but still nothing.
Anyway, Im looking at grabbing a Garmin GPS18 LVC, they are only just
over
toying with setting up my old Garmin GPS12 as a reference
for a
server (FreeBSD 6.2) running ntpd, but Ive run into an issue.
Is it possible the issue isn't what you think it is?
Ive searched around a bit and cant find an answer, perhaps because
there
isnt one.
I once (years ago) had
Having read the man page (also, ntp.conf(5)), it is not apparent that
there is a way to tell it to bind only to a particular interface (or
particular interfaces). It would be nice if there is actually such a
feature, so I figured I'd ask.
Definitely not a major problem is this isn't possible
in occasional calcru errors (see my
recent post on that subject), and reading the overbrief
manpage requires remembering to run man -M /usr/local ntpd.
I did say straightforward, right? ;-)
___
freebsd-questions@freebsd.org mailing list
http
time I reboot my server, I get two ntpd processes:
[EMAIL PROTECTED] ps -U root | grep ntpd
PID TT STAT TIME COMMAND
571 ?? Ss 0:00.12 /usr/sbin/ntpd -c /etc/ntp.conf -p
/var/run/ntpd.pid
686 ?? S 0:00.00 /usr/sbin/ntpd -c /etc/ntp.conf -p
/var/run/ntpd.pid
When I
I'm running FreeBSD 7.0, and I have 'ntpd_enable=YES' in my /etc/rc.conf.
Every time I reboot my server, I get two ntpd processes:
[EMAIL PROTECTED] ps -U root | grep ntpd
PID TT STAT TIME COMMAND
571 ?? Ss 0:00.12 /usr/sbin/ntpd -c /etc/ntp.conf -p
/var/run/ntpd.pid
686 ?? S
On Thu, Jun 12, 2008 at 02:17:46PM -0700, Nerius Landys wrote:
I'm running FreeBSD 7.0, and I have 'ntpd_enable=YES' in my /etc/rc.conf.
Every time I reboot my server, I get two ntpd processes:
[EMAIL PROTECTED] ps -U root | grep ntpd
PID TT STAT TIME COMMAND
571 ?? Ss 0
Hi,
I run current 70-STABLE and after few days ntpd stops responding queries
like 'ntpq -c rv localhost' and time begins to drift.
Anyone observes the same problem?
Yuri
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
I've installed ntp-4.2.4p4 from ports on a FreeBSD 6.3/i386 system.
The ntpd process does not start at boot time. These lines exists in
/etc/rc.conf:
ntpd_enable=YES
ntpd_program=/usr/local/bin/ntpd
ntpd_flags=-c /etc/ntp.conf -p /var/run/ntpd.pid
ntpd_sync_on_start=YES
Manually running
On Thu, Apr 24, 2008 at 06:39:46AM -0700, David Newman wrote:
I've installed ntp-4.2.4p4 from ports on a FreeBSD 6.3/i386 system.
The ntpd process does not start at boot time. These lines exists in
/etc/rc.conf:
ntpd_enable=YES
ntpd_program=/usr/local/bin/ntpd
ntpd_flags=-c /etc
On 4/24/08 7:47 AM, Daniel Bye wrote:
{
rc_flags=-c ${ntpd_config} ${ntpd_flags}
You need to set ntpd_config to the path to your config file - as it is
now, you are also setting it in ntpd_flags, which the above line then
expands to something like this:
rc_flags=-c
Hi list,
is it normal to have two ntpds?
767 ?? Ss 0:37.28 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid
844 ?? S 0:00.95 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid
Regards
Ivan
-
Looking for last minute shopping deals
In response to Fred Condo [EMAIL PROTECTED]:
On Feb 15, 2008, at 9:24 AM, ivan dimitrov wrote:
Hi list,
is it normal to have two ntpds?
767 ?? Ss 0:37.28 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/
ntpd.pid
844 ?? S 0:00.95 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run
On Fri, Feb 15, 2008 at 09:24:23AM -0800, ivan dimitrov wrote:
Hi list,
is it normal to have two ntpds?
767 ?? Ss 0:37.28 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid
844 ?? S 0:00.95 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid
This double ntpd problem has
On Feb 15, 2008, at 9:24 AM, ivan dimitrov wrote:
Hi list,
is it normal to have two ntpds?
767 ?? Ss 0:37.28 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/
ntpd.pid
844 ?? S 0:00.95 /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/
ntpd.pid
Regards
Ivan
No:
[EMAIL PROTECTED
On Thu, Jan 31, 2008 at 01:35:55AM -0800, Rudy wrote:
...
Can ntpd update the system clock from within a jail?
That is not possible.
You have to update the system clock on the host system.
--
Oliver PETER, email: [EMAIL PROTECTED], ICQ# 113969174
Worker bees can leave. Even drones can fly
Will this work?
/usr/sbin/jail /var/chroot/ntp ntp.monkeybrains.net 10.10.10.10 \
/usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid
Can ntpd update the system clock from within a jail?
Here is the layout of my jail
# find /var/chroot/ntp/
/var/chroot/ntp/
/var/chroot/ntp/lib
/var/chroot
On Dec 12, 2007, at 9:57 PM, N.J. Thomas wrote:
* jekillen [EMAIL PROTECTED] [2007-12-12 20:42:47-0800]:
Q: When making changes to ntp.conf it is necessary to restart the
server?
According to the ntpd docs, yes. The ntpd configuration docs say this:
Ordinarily, ntpd reads the ntp.conf
Hello:
Q: When making changes to ntp.conf it is necessary to restart the
server?
(I suspect yes)
Q: How is that done?
(I suspect ntpd reload or restart per rc script.. along the lines of
apachectl restart
or postfix reload??? Kill -HUP pid ??? )
I am looking at FreeBSD handbook and ntp
* jekillen [EMAIL PROTECTED] [2007-12-12 20:42:47-0800]:
Q: When making changes to ntp.conf it is necessary to restart the
server?
According to the ntpd docs, yes. The ntpd configuration docs say this:
Ordinarily, ntpd reads the ntp.conf configuration file at startup
time in order
On Thu, 1 Nov 2007 22:46:56 -0400
N.J. Thomas [EMAIL PROTECTED] wrote:
* jekillen [EMAIL PROTECTED] [2007-11-01 15:43:53 -0800]:
These are the servers I have listed:
[...]
I suppose I should find ones that are reachable via ipv4.
Better yet, use the NTP Pool Project. If you including the
* RW [EMAIL PROTECTED] [2007-11-02 14:34:05 +]:
server 0.pool.ntp.org prefer
server 1.pool.ntp.org prefer
server 2.pool.ntp.org prefer
You don't need any of the prefers. Using prefer like this simply
disables the clustering algorithm, and degrades the accuracy.
Yeah, I had copied
* [EMAIL PROTECTED] [2007-10-31 16:08:10 -0800]:
I set up ntpd on FreeBSD 6.2 and am getting complaints from ntpd
that there is no route to such and such address. It gives what
appears to be an interface card address.
ntpq -p
remote refid st t when poll reach
On Nov 1, 2007, at 11:18 AM, N.J. Thomas wrote:
* [EMAIL PROTECTED] [2007-10-31 16:08:10 -0800]:
I set up ntpd on FreeBSD 6.2 and am getting complaints from ntpd
that there is no route to such and such address. It gives what
appears to be an interface card address.
ntpq -p
remote
* jekillen [EMAIL PROTECTED] [2007-11-01 15:43:53 -0800]:
These are the servers I have listed:
[...]
I suppose I should find ones that are reachable via ipv4.
Better yet, use the NTP Pool Project. If you including the following in
your ntp.conf:
server 0.pool.ntp.org prefer
server
Jeff,
I set up ntpd on FreeBSD 6.2 and am getting complaints from ntpd that
there is no route to such and such address. It gives what appears to be
an interface card address.
As a general rule, please copy/paste the error message.
The
rest respond without hesitation, both to dig and ping
1 - 100 of 308 matches
Mail list logo
