Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For those alarmed at the offset...

# yum install ntpdate

# ntpdate -u ntp-1.vt.edu

# hwclock -w

"Your time is exact!"



ntpdate is dead and is discontinued. Use an actual daemon to govern your time source.

I thought redhat installed ntpd or chrony by default. I know chrony is the default for the next fedora release. If you have ntpd/chronyd installed your advice is horrible and not just because you pointed everyone to Virginia Tech's time server.


Thanks : Updated procedure (for Fedora without chronyd/ntpd running already) :

# yum install chrony

# systemctl enable chronyd.service

# systemctl start chronyd.service

Sorry if the (working) pointers before were horrible. Hopefully this is more useful - the servers used are {N}.fedora.pool.ntp.org.


chronyd is a lot more mindful of battery/power considerations than ntpd. It is an interesting approach to endpoint time synchronization compared to the ntp reference implementation.


This is an unobtrusive app that does the job for Android (root required/recommended): https://play.google.com/store/apps/details?id=ru.org.amip.Cl...

My ZTE Blade/CM7 was obnoxiously bad at keeping time, probably a software bug or something.


Not sure why Android does not have ntp built in. My network does not broadcast a time signal, maybe it is just assumed they all do.


Your cell network or you do not have multicast ntp enabled?


Cell network doesnt broadcast time. You can install ntp client, but it needs to run as root, and I wont let anything from the market run as root, and I havent got around to building an ntp client myself...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: