search for: ntpd_enabl

Displaying 5 results from an estimated 5 matches for "ntpd_enabl".

Did you mean: ntpd_enable
2007 Sep 07
0
cannot access samba server
....0.1" ifconfig_vr0="inet 192.168.0.80 netmask 255.255.255.0" usbd_enable="YES" lpd_enable="YES" moused_port="/dev/psm0" moused_type="auto" moused_enable="YES" ntpdate_flags="0.us.pool.ntp.org" ntpdate_enable="YES" ntpd_enable="YES" snmpd_enable="YES" rpcbind_enable="YES" nfs_server_enable="YES" nfs_server_flags="-u -t -n 4" mountd_flags="-r" amd_enable="YES" inetd_enable="YES" sshd_enable="YES" font8x16="iso15-8x16" #...
2011 May 08
6
ntp revisited (so what to do ?)
OK, So what you people say is : 1. Run "ntpdate" during startup only once 2. After that, keep time with ntpd Right ? Regards, spyros ---- "I merely function as a channel that filters music through the chaos of noise" - Vangelis
2008 Mar 04
1
FreeBSD 7.9-stable: weird messages in /var/log/messages?
Hello One one of my stable machines I see these messages in /var/log/messages: Mar 3 18:37:41 kg-i82 kernel: 16.011e9e3975b3aa06 too long Mar 3 21:41:42 kg-i82 kernel: 16.016a24cf0742715c too long Mar 3 21:41:58 kg-i82 kernel: 15.feb784aee196608c too short Does anyone know hwat the messages mean, or which part of the kernel they are from? Googling didn't help me. The machine runs FreeBSD
2007 Mar 08
16
CFengine into Puppet
I finally got my cfengine configs all objectified and separated into service-based configurations. But there are still many things that cfe can''t or won''t do very well, so I''m looking for a replacement. What about puppet? I am looking for something that I can use to manage services and applications, not hosts and files. It seems like puppet may have inherited some of
2013 Jun 19
3
shutdown -r / shutdown -h / reboot all hang and don't cleanly dismount
Hello -STABLE@, So I've seen this situation seemingly randomly on a number of both physical 9.1 boxes as well as VMs for I would say 6-9 months at least. I finally have a physical box here that reproduces it consistently that I can reboot easily (ie; not a production/client server). No matter what I do: reboot shutdown -p shutdown -r This specific server will stop at "All buffers