I am exploring changing the way our remote openSUSE systems (not connected to the internet) maintain proper time. We have GPS devices in these system, but have thus far only used the time for our own devious purposes. We have never tried to maintain the system time. The popular wisdom on the gpsd list (all things related to GPS access on Linux) is that one should use chrony (http://chrony.tuxfamily.org) rather then NTP for this purpose. The reason given is that NTP does not deal well with a time source that is perhaps seldom available. See http://chrony.tuxfamily.org/FAQ.html#question_2.1 In order to use chrony, hwclock must be disabled on system shutdown. This is because chrony would like to be the one that sets the clock when the system comes up - perhaps without a GPS time source - but keeping the time as close to correct as possible. If, on openSUSE systems, I disable hwclock on shutdown only, what madness might ensue? I don't mean 'Will the time be wrong?' I assume that chrony will take care of that. But perhaps there are some other system activities that are dependent on hwclock running at shutdown? Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org