- Thread Starter
- #26
I'll run
I take it because
Also, you can ignore the part in my last reply where I ask if I should run
From my vantage point, at this point the issue seems like it's with ntpd. I did run
# ntpdate 0.freebsd.pool.ntp.org
as a last resort because that seems like manually setting the clock. I would prefer to get my clock fixed so the system automatically sets the time.I take it because
service ntpd status
doesn't alter the state of the whole system (see below), you wanted me to run it as a regular user, not root. But, still, shouldn't that command have returned that ntpd is running?Also, you can ignore the part in my last reply where I ask if I should run
service ntpd start
and if I should run the command as root. It is my understanding, based on my other thread, that that command would want to be run as root, but also that ntpd should have automatically started after the first reboot, anyway.Thanks!You'll soon get a feeling for this. As a rule of thumb: All commands which alter the state of the whole system need root privileges.
From my vantage point, at this point the issue seems like it's with ntpd. I did run
# service ntpd status
as root (I take it this was safe, but it's probably better to run that command as a regular user), and it still says it's not running.I will try running that command then. But would a better way for writing the command/syntax beThe cool thing about sysrc(8) is that you can run it as many times as you want. All this does it making surentpd_enable="YES"
is set in rc.conf, if it's already there it won't change anything. If it's not, it will get added.
# sysrc ntpd_enable="YES"
(note the quotation marks)? I just see that's how the other lines are written in /etc/rc.conf. Thanks for the rest of your post; I read it after I had already begun writing my reply.