netwait_timeout, which defaults to 60 in
/etc/defaults/rc.conf.
I've finally got a combination of suggested configurations that get me
to where I want to be (using ntpd, ntpdate, and netwait).
However, I've found that I still need ntpdate_enable=YES rather than
ntpd_sync_on_start=YES. The reason
On 11/05/2011 14:52, Robert Simmons wrote:
Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?
After setting ntpdate_enable=YES in rc.conf, I get the following
error on boot:
Setting date via ntp.
Error : hostname
Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?
After setting ntpdate_enable=YES in rc.conf, I get the following
error on boot:
Setting date via ntp.
Error : hostname nor servname provided, or not known
5 Nov 17
Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?
After setting ntpdate_enable=YES in rc.conf, I get the following
error on boot:
Setting date via ntp.
Error : hostname nor servname provided, or not known
5 Nov 17
before running ntpdate at boot on a box with a static IP address?
After setting ntpdate_enable=YES in rc.conf, I get the following
error on boot:
Setting date via ntp.
Error : hostname nor servname provided, or not known
5 Nov 17:11:05
ntpdate[786]: can't find host 0.freebsd.pool.ntp.org
On Sat Nov 5 11, Robert Simmons wrote:
Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?
After setting ntpdate_enable=YES in rc.conf, I get the following
error on boot:
Setting date via ntp.
Error
that is running on bare metal, no VM. Fixed IP
address (198.162) behind a NAT firewall.
But, after booting, everything works correctly:
# /etc/rc.d/ntpdate onestart
Setting date via ntp.
5 Nov 18:09:31 ntpdate[1324]: step time server 128.10.254.7 offset
-0.000537 sec
This happens when
On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best arun...@freebsd.org wrote:
same here. simply add something like the following to your crontab:
0 10 * * */2 /etc/rc.d/ntpdate onestart
I have something similar in my crontab which is not exactly what I
need. I want
The keywords in /etc/rc.d/ntpdate have
# PROVIDE: ntpdate
# REQUIRE: NETWORKING syslogd named
# KEYWORD: nojail
which means that networking must be up first. The question in your
case is why name resolution is failing.
See what happens if you pick some public stratum 1 or stratum 2
servers
On 05/11/2011 22:19, Robert Simmons wrote:
On Sat, Nov 5, 2011 at 6:03 PM, Alexander Best arun...@freebsd.org wrote:
same here. simply add something like the following to your crontab:
0 10 * * */2 /etc/rc.d/ntpdate onestart
I have something similar in my crontab
On Sat, 5 Nov 2011, Robert Simmons wrote:
Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?
After setting ntpdate_enable=YES in rc.conf, I get the following
error on boot:
Setting date via ntp.
Error : hostname
On Sat, Nov 5, 2011 at 6:55 PM, Warren Block wbl...@wonkity.com wrote:
On Sat, 5 Nov 2011, Robert Simmons wrote:
Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?
Yes, it is. FreeBSD 8-STABLE and 9 have /etc/rc.d
On Sat, Nov 5, 2011 at 6:33 PM, Matthew Seaman
m.sea...@infracaninophile.co.uk wrote:
crontabs have this handy '@reboot' syntax... It's all explained in
crontab(5).
Thanks!
However, you would be well advised to run ntpd(8) rather than bodging
the clock with ntpdate at intervals. ntpdate
On Sat, 5 Nov 2011, Robert Simmons wrote:
On Sat, Nov 5, 2011 at 6:55 PM, Warren Block wbl...@wonkity.com wrote:
On Sat, 5 Nov 2011, Robert Simmons wrote:
Is there a way to make sure that the interface is UP and working
before running ntpdate at boot on a box with a static IP address?
Yes
On Sat, 5 Nov 2011, d...@safeport.com wrote:
On Sat, 5 Nov 2011, Warren Block wrote:
On Sat, 5 Nov 2011, Robert Simmons wrote:
I've had this problem with machines using DHCP and the solution was to
use SYNCDHCP rather than DHCP in rc.conf. However, this box is using
a static IP address.
a combination of suggested configurations that get me
to where I want to be (using ntpd, ntpdate, and netwait).
However, I've found that I still need ntpdate_enable=YES rather than
ntpd_sync_on_start=YES. The reason for this is that I'm running at
securelevel 3, and ntpd takes too long to get up
/ntpdate onestart
I have something similar in my crontab which is not exactly what I
need. I want to make sure that the clock is set at every boot because
I'm using this as a kerberos server. If the clock is not set properly
at boot, kerberos will not work properly until the nightly cron jobs
2010/3/13 Randal L. Schwartz mer...@stonehenge.com
But really, why are you using ntpdate and not just ntpd?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/
Smalltalk/Perl/Unix consulting, Technical
with ntpdate(8) can cause nasty effects like time apparently going
backwards -- and that will seriously upset a lot of software.
Also, it doesn't account for the natural clock drift of your system, so
it's going to give you pretty terrible accuracy -- probably good to no
more than a few seconds. ntpdate(8
While not having been part of this discussion I just want to say thanks
for the tips. I've used them to cease using ntpdate as well and am
already synced with a time server I know to be constantly reliable.
--
Yours In Christ,
PIT
Emails are not formal business letters, whatever businesses may
a kind of habit.
It's a bad habit you should try and cure yourself of. Stepping the
clock with ntpdate(8) can cause nasty effects like time apparently
going backwards -- and that will seriously upset a lot of software.
Also, it doesn't account for the natural clock drift of your system,
so
On 03/13/10 13:08, RW wrote:
snip
ntpd_sync_on_start=YES
snip
you can run ntpdate at boot with
ntpdate_enable=YES
the rc script gets the servers from ntp.conf
Can you have both in rc.conf without abusing the ntp server(s) or should
it just be one or the other? I'd like my clock
On Sat, Mar 13, 2010 at 01:19:54PM -0600, Programmer In Training wrote:
On 03/13/10 13:08, RW wrote:
snip
ntpd_sync_on_start=YES
snip
you can run ntpdate at boot with
ntpdate_enable=YES
the rc script gets the servers from ntp.conf
Can you have both in rc.conf without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/03/2010 19:08:38, RW wrote:
ntpd_sync_on_start=YES
is not a complete substitute for running ntpdate at startup. It allows
ntpd to make a large correction, but it doesn't block the boot sequence
so you could still get a large step-change
I have the following line in my root cron:
5 * * * * /usr/sbin/ntpdate ru.pool.ntp.org /dev/null
That must hourly adjust system time via NTP.
But I discover that it works from time to time: some days just once, some
days 5-6 times a day I receive e-mail with text like
12 Mar 12:05:05 ntpdate
Антон Клесс skrev 2010-03-12 11:57:
I have the following line in my root cron:
5 * * * * /usr/sbin/ntpdate ru.pool.ntp.org /dev/null
That must hourly adjust system time via NTP.
But I discover that it works from time to time: some days just once, some
days 5-6 times a day I receive e-mail
man ntpdate:
-s Divert logging output from the standard output (default) to the
system syslog(3) facility. This is designed primarily for
conve-
nience of cron(8) scripts.
Change your cron job to
5 * * * * /usr/sbin/ntpdate -s ru.pool.ntp.org
On Fri, 12 Mar 2010 09:22:07 -0500
Nathan Vidican nat...@vidican.com wrote:
or more specifically, if you don't want to leave ntpd running,
read-up on 'ntpd -q' which mimmicks the behavior of ntpdate but
allows you to use multiple ntp servers.
ntpdate supports multiple servers too, you just
So, while ru.pool.ntp.org is pool of several servers, I have to run it as
5 * * * * /usr/sbin/ntpdate ru.pool.ntp.org ru.pool.ntp.org
ru.pool.ntp.org /dev/null
to check 3 servers from pool?
2010/3/12 RW rwmailli...@googlemail.com
On Fri, 12 Mar 2010 09:22:07 -0500
Nathan Vidican nat
On Fri, 12 Mar 2010 18:06:45 +0300
Антон Клесс antoniok@gmail.com wrote:
So, while ru.pool.ntp.org is pool of several servers, I have to run
it as
5 * * * * /usr/sbin/ntpdate ru.pool.ntp.org ru.pool.ntp.org
ru.pool.ntp.org /dev/null
to check 3 servers from pool?
You can different
RW == RW rwmailli...@googlemail.com writes:
RW You can different servers like this:
RW 0.ru.pool.ntp.org
RW 1.ru.pool.ntp.org
RW 2.ru.pool.ntp.org
RW 3.ru.pool.ntp.org
But really, why are you using ntpdate and not just ntpd?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1
.
It works for me at LAN, but I didn't manage to sync time by
ntpdate at start time either when using PPPoE at my friends home.
Seems that the network interface/something else is not
ready at the time ntpdate fires. May be setting:
-
rc_debug=YES
-
at /etc/rc.conf[.local] will be helpful
and in rc.conf I have:
ntpdate_enable=YES
ntpdate_hosts=ntp1.cs.wisc.edu
When I boot computer I get a message there are no this host but when I run
/usr/sbin/ntpdate ntp1.cs.wisc.edu it works.
I had the same in rc.conf on FreeBSD 7.2 and it works all the time. All
settings on FreeBSD8.0
time by
ntpdate at start time either when using PPPoE at my friends home.
Seems that the network interface/something else is not
ready at the time ntpdate fires. May be setting:
-
rc_debug=YES
-
at /etc/rc.conf[.local] will be helpful.
On Sun, Nov 29, 2009 at 8:39 PM, ajtiM lum
/ntpdate ntp1.cs.wisc.edu it works.
I had the same in rc.conf on FreeBSD 7.2 and it works all the time. All
settings on FreeBSD8.0 are the same as I had on 7.2.
Might you have a Realtek network card?
-Warren Block * Rapid City, South Dakota USA
Yes, I have realtek card too
but when I
run /usr/sbin/ntpdate ntp1.cs.wisc.edu it works.
I had the same in rc.conf on FreeBSD 7.2 and it works all the time. All
settings on FreeBSD8.0 are the same as I had on 7.2.
Might you have a Realtek network card?
Yes, I have realtek card too but it is not active. DHCP is on sk0
a message there are no this host but when I
run /usr/sbin/ntpdate ntp1.cs.wisc.edu it works.
I had the same in rc.conf on FreeBSD 7.2 and it works all the time. All
settings on FreeBSD8.0 are the same as I had on 7.2.
Might you have a Realtek network card?
-Warren Block
Hi!
I have new installed FreeBSD 8.0 and in rc.conf I have:
ntpdate_enable=YES
ntpdate_hosts=ntp1.cs.wisc.edu
When I boot computer I get a message there are no this host but when I run
/usr/sbin/ntpdate ntp1.cs.wisc.edu it works.
I had the same in rc.conf on FreeBSD 7.2 and it works all
On Sun, 29 Nov 2009 20:39:32 -0600
ajtiM lum...@gmail.com wrote:
Hi!
I have new installed FreeBSD 8.0 and in rc.conf I have:
ntpdate_enable=YES
ntpdate_hosts=ntp1.cs.wisc.edu
When I boot computer I get a message there are no this host but
when I run /usr/sbin/ntpdate ntp1.cs.wisc.edu
On Sun, 29 Nov 2009, ajtiM wrote:
I have new installed FreeBSD 8.0 and in rc.conf I have:
ntpdate_enable=YES
ntpdate_hosts=ntp1.cs.wisc.edu
When I boot computer I get a message there are no this host but when I run
/usr/sbin/ntpdate ntp1.cs.wisc.edu it works.
I had the same in rc.conf
Jonathan Horne wrote:
On Sunday 02 July 2006 15:49, Erik Nørgaard wrote:
There is a dhcp-option, ntp-servers, to set which ntp-server to use. It
would be quite useful with ntpdate. Does anyone have a patch to ntpdate
startup script or other hack that use this option? - just before I start
Hi:
There is a dhcp-option, ntp-servers, to set which ntp-server to use. It
would be quite useful with ntpdate. Does anyone have a patch to ntpdate
startup script or other hack that use this option? - just before I start
hacking myself...
Thanks, Erik
--
Ph: +34.666334818
On Sunday 02 July 2006 15:49, Erik Nørgaard wrote:
Hi:
There is a dhcp-option, ntp-servers, to set which ntp-server to use. It
would be quite useful with ntpdate. Does anyone have a patch to ntpdate
startup script or other hack that use this option? - just before I start
hacking myself
Thanks for the return! I've discovered my ISP has apparently shut off
port 123 (NTP), and if I dontpdate -u ntp.cape.comI get my
time set! But ntpq lacks ntpdate's option to use an unprivileged port.
I guess time is come to ask my ISP. (Shouldn't I have done tha before :-]
Again
On Sat, 17 Jun 2006 21:30:55 -0400 (EDT)
Charles Bacon [EMAIL PROTECTED] wrote:
Since FreeBSD 4.5-Release, I have been unable to get NTP working on
my two FreeBSD computers, one running 5.3Release and the other on
6.1Release. I have done nothing with the GENERIC kernel on either
machine. I
Since FreeBSD 4.5-Release, I have been unable to get NTP working on
my two FreeBSD computers, one running 5.3Release and the other on
6.1Release. I have done nothing with the GENERIC kernel on either
machine. I talk SSH between them, and have been running ntpd on
both, each naming the other as
On 11/16/05, dick hoogendijk [EMAIL PROTECTED] wrote:
On Wed, 16 Nov 2005 17:15:24 +0200
Ivailo Tanusheff [EMAIL PROTECTED] wrote:
Why you need to do this?
Your system is not fully operationl in the time you try to run
ntpdate. Just edit your /etc/ntp.conf to connect to some time
On 11/17/05, Bob Johnson [EMAIL PROTECTED] wrote:
On 11/16/05, dick hoogendijk [EMAIL PROTECTED] wrote:
On Wed, 16 Nov 2005 17:15:24 +0200
Ivailo Tanusheff [EMAIL PROTECTED] wrote:
Why you need to do this?
Your system is not fully operationl in the time you try to run
ntpdate. Just
Andrew P. wrote:
On 11/17/05, Bob Johnson [EMAIL PROTECTED] wrote:
[ ... ]
Leading numbers are not necessary in most cases.
I use:
server europe.pool.ntp.org
server europe.pool.ntp.org
server europe.pool.ntp.org
That selects 3 random servers from the whole
europe pool.
The point of using
Why you need to do this?
Your system is not fully operationl in the time you try to run ntpdate.
Just edit your /etc/ntp.conf to connect to some time servers. Per example
mine is:
-su-2.05b# cat /etc/ntp.conf
server ntp2.usno.navy.mil
server tock.usno.navy.mil
server tick.usno.navy.mil
server
On Wed, 16 Nov 2005 17:15:24 +0200
Ivailo Tanusheff [EMAIL PROTECTED] wrote:
Why you need to do this?
Your system is not fully operationl in the time you try to run
ntpdate. Just edit your /etc/ntp.conf to connect to some time
servers. Per example mine is:
[cut very nice example]
Thank you
On 11/16/05, dick hoogendijk [EMAIL PROTECTED] wrote:
On Wed, 16 Nov 2005 17:15:24 +0200
Ivailo Tanusheff [EMAIL PROTECTED] wrote:
Why you need to do this?
Your system is not fully operationl in the time you try to run
ntpdate. Just edit your /etc/ntp.conf to connect to some time
Andrew P. wrote:
On 11/16/05, dick hoogendijk [EMAIL PROTECTED] wrote:
[ ... ]
Thank you. I
You are probably right. I'll get rid of ntpdate in rc.conf.
I have two timeservers at the moment. I will look for some more in the
Netherlands. Yours are to far away ;-)
Last time I checked ntpd docs
On Wed, Nov 16, 2005 at 12:09:45PM -0500, Chuck Swiger wrote:
[...]
Running ntpdate -b at boot to forcibly syncronize the clock is a pretty
good idea, but you actually can convince ntpd to sync even a clock which is
badly off via:
-g Normally, ntpd exits if the offset exceeds
I have a ntpdate -b server rule in my rc.conf before the ntpd daemon
starts up. I get error msgs that the time server cannot be found.
Is named run before or after ntpdate?
Should I change the rule in something like ntpdate -b ip ?
What is the rule of thumb?
--
dick -- http://nagual.st/ -- PGP
dick hoogendijk schrieb:
I have a ntpdate -b server rule in my rc.conf before the ntpd daemon
starts up. I get error msgs that the time server cannot be found.
Is named run before or after ntpdate?
Should I change the rule in something like ntpdate -b ip ?
What is the rule of thumb?
According
On 11/15/05, dick hoogendijk [EMAIL PROTECTED] wrote:
I have a ntpdate -b server rule in my rc.conf before the ntpd daemon
starts up. I get error msgs that the time server cannot be found.
Is named run before or after ntpdate?
Should I change the rule in something like ntpdate -b ip ?
What
Hi there-
I need your help. I tried get ntpdate work inside the Jail and it wont
let me set the clock.
The parent works correct time but inside the jail wont let me update
correct time clock. How do I get correct clock set inside the jail. Let me
know thanks!
PS. Do i have to kill the Jail
Never mind.. Please discard this. I successful correct the timezone inside
the jail.
thanks anyway!
At 11:42 AM 8/10/2003 -0700, fasty wrote:
Hi there-
I need your help. I tried get ntpdate work inside the Jail and it wont
let me set the clock.
The parent works correct time but inside
On Mon, 28 Oct 2002, Kent Stewart wrote:
ntpdate_enable=YES # Run ntpdate to sync time on boot (or NO).
ntpdate_program=/usr/sbin/ntpdate # path to ntpdate, if you want a different
one.
ntpdate_flags=-b clock.isc.org # Flags to ntpdate (if enabled).
My clock
On Tue, 29 Oct 2002, Jacob Rhoden wrote:
Are you in the right time zone? If you are in australia, you have to set
preciscely where you are for it to work (for example, here in melbourne our
time zone just went back an our for summer). Dont know if this may help, but
i would guess that is what
On Sun, 3 Nov 2002, at 17:52 [=GMT-0500], Peter Leftwich wrote:
But I wonder why there is no unix
standard command to view and/or set the PC's current timezone!
Perhaps I don't understand your problem? What is wrong with 'date'?
voo:marc {783} date
Mon Nov 4 00:12:38 CET 2002
So I have CET
# [EMAIL PROTECTED] / 2002-10-28 20:11:41 -0800:
I thought I had this in my /etc/rc.conf but didn't, so I added the
following lines and rebooted:
ntpdate_enable=YES # Run ntpdate to sync time on boot (or NO).
ntpdate_program=/usr/sbin/ntpdate # path to ntpdate, if you want
* Peter Leftwich [Tuesday 29 October 2002 04:11 am]
I thought I had this in my /etc/rc.conf but didn't, so I added the
following lines and rebooted:
ntpdate_enable=YES # Run ntpdate to sync time on boot (or
NO). ntpdate_program=/usr/sbin/ntpdate # path to ntpdate, if you
Peter Leftwich wrote:
I thought I had this in my /etc/rc.conf but didn't, so I added the
following lines and rebooted:
ntpdate_enable=YES # Run ntpdate to sync time on boot (or NO).
ntpdate_program=/usr/sbin/ntpdate # path to ntpdate, if you want a different one.
ntpdate_flags
65 matches
Mail list logo
