![]() Also the Yahoo group can be useful, but is low on recent posts only I have posted about this issue there so far. such as setting up startup scripts and writing to NVRAM see In case you don't already know this, for general info. I've experimented with turning on the media server and found it no longer hogging the CPU, but I turned it off again. ![]() HWCLOCK is then in sync with the system clock (other than the 16-year error) and they start to drift apart, until synced again the next day, and so far the system date's year has stayed at 2016. But it seems okay and I see that each day (I also changed it so that the ntp server is read daily instead of every 3 days by changing ntp_interval to 24 from 72) it also writes it to hwclock. This appears to be working after a couple of days, though I would have thought that "sync TO hwclock" meant going in the other direction, that is TO the system clock. What I'm trying now is that I set in nvram sync_to_hwclock_interval to 24000000 instead of 24, so it won't happen for about 2700 years. However, I believe that after 24 hours, the system reads the hardware clock into the system time again, restoring the error. The system time is quickly corrected after boot when the time is read from an ntp server. I found that the hardware clock (hwclock) will incorrectly set the year to 2032 if copying from the system time starting in 2016 (hwclock -s). ![]() This resulted in the media server process ms-mips hogging the CPU, even though I turned off media serving on all folders - I had to kill the ms-mips process, ultimately by adding a startup script to do so. Business PCs, Workstations and Point of Sale Systems.Printer Wireless, Networking & Internet.DesignJet, Large Format Printers & Digital Press.Printing Errors or Lights & Stuck Print Jobs.Notebook Hardware and Upgrade Questions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |