Difference between revisions of "Talk:Initscripts/rc.conf"
Thestinger (talk | contribs) m |
(→Localization) |
||
| Line 1: | Line 1: | ||
= Localization = | = Localization = | ||
| − | Can't HARDWARECLOCK also be set to ntp? -- | + | Can't HARDWARECLOCK also be set to ntp? -- [[User:piezoelectric|piezoelectric]] |
| − | no - setting it to ntp, blank, null, or anything else just stops adjtime from running and disables the hwclock load in rc.sysinit and save in rc.shutdown [[User:Thestinger|Thestinger]] 13:51, 7 April 2010 (EDT) | + | :no - setting it to ntp, blank, null, or anything else just stops adjtime from running and disables the hwclock load in rc.sysinit and save in rc.shutdown [[User:Thestinger|Thestinger]] 13:51, 7 April 2010 (EDT) |
| + | |||
| + | ::I see that, but there might be some mention that HARDWARECLOCK shouldn't be UTC or localtime if the user wants to use NTP (which I suspect a lot of people do). -- [[User:Piezoelectric|Piezoelectric]] 10:15, 11 April 2010 (EDT) | ||
Revision as of 14:15, 11 April 2010
Localization
Can't HARDWARECLOCK also be set to ntp? -- piezoelectric
- no - setting it to ntp, blank, null, or anything else just stops adjtime from running and disables the hwclock load in rc.sysinit and save in rc.shutdown Thestinger 13:51, 7 April 2010 (EDT)
- I see that, but there might be some mention that HARDWARECLOCK shouldn't be UTC or localtime if the user wants to use NTP (which I suspect a lot of people do). -- Piezoelectric 10:15, 11 April 2010 (EDT)