On 6 November 2011 02:51, Robert Simmons rsimmo...@gmail.com wrote:
On Sat, Nov 5, 2011 at 7:43 PM, Warren Block wbl...@wonkity.com wrote:
netwait_enable=YES
netwait_ip=192.168.1.1 # IP address to ping to verify network is up
netwait_if=em0 # interface to use
Also there's
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
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
Are you running a firewall? Do you have a ppp connection?
This happens when there is a dependency that is not expressed in the
/etc/rc.d scripts.
- M
On Sat, Nov 5, 2011 at 2:52 PM, Robert Simmons rsimmo...@gmail.com wrote:
Is there a way to make sure that the interface is UP and working
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 :
On Sat, Nov 5, 2011 at 5:57 PM, Michael Sierchio ku...@tenebras.com wrote:
Are you running a firewall? Do you have a ppp connection?
I'm not running a firewall on the machine in question. I am behind a
firewall, if that's what you mean. I don't have a ppp connection.
The box is a server that
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 to
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 for
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
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 is
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.
On Sat, Nov 5, 2011 at 7:43 PM, Warren Block wbl...@wonkity.com wrote:
netwait_enable=YES
netwait_ip=192.168.1.1 # IP address to ping to verify network is up
netwait_if=em0 # interface to use
Also there's netwait_timeout, which defaults to 60 in /etc/defaults/rc.conf.
I've finally got a
Matthew Seaman m.sea...@infracaninophile.co.uk writes:
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
17 matches
Mail list logo
