It would appear that on Jul 13, C Anthony Risinger did say:
On Jul 12, 2011 8:19 AM, Joe(theWordy)Philbrook jtw...@ttlc.net wrote:
snip
Dude ... just set UTC and forget about it ... forever :-)
The wisdom of others frees time to build more wisdom of self.
Dde ... If my
It would appear that on Jul 12, Tom Gundersen did say:
On Jul 12, 2011, at 15:18, Joe(theWordy)Philbrook jtw...@ttlc.net wrote:
Whereas If I put ntpd -qg
in rc.local there is sometimes enough time to type my username before the
NTP based time adjustment can be seen to occur..
Yes,
On Sat, Jul 16, 2011 at 11:36:45AM -0400, Joe(theWordy)Philbrook wrote:
It would appear that on Jul 12, Tom Gundersen did say:
It would appear that your pre-quotation messages are annoying.
[snip]
Actually I wouldn't notice the adjustment at all except that certain
system messages put
On Sat, Jul 16, 2011 at 5:36 PM, Joe(theWordy)Philbrook jtw...@ttlc.net wrote:
myhost login: jtwd
NTP: adjust RTC [012.001]yp
Password:
Or some such thing. So unless the ntpd called from rc.local is NOT supposed
to leave a message on tty1, I don't think that's a bug.
Ah, I
Le mardi 12 juillet 2011 à 20:41 +0200, Tom Gundersen a écrit :
No, we adjust the time as soon as possible to minimize the problems (though
we are not able to eliminate the gap when the time is wrong, so we simply
don't know what might go wrong, the more init is optimized, the more likely
even though I have switch to HARDWARECLOCK=UTC,
rtkit-daemon line date time in logs are still wrong. in UTC ??
what's the matter with it ?
On Jul 12, 2011 8:19 AM, Joe(theWordy)Philbrook jtw...@ttlc.net wrote:
snip
Dude ... just set UTC and forget about it ... forever :-)
The wisdom of others frees time to build more wisdom of self.
C Anthony
It would appear that on Jul 11, Tom Gundersen did say:
On Mon, Jul 11, 2011 at 7:31 PM, Joe(theWordy)Philbrook jtw...@ttlc.net
wrote:
NOT dual-boot, Multi-boot, And I don't think in UTC see above
The more OS'es you have, the better reason to keep RTC in UTC. You
shouldn't need to
Replying from phone, sorry fir brevity.
On Jul 12, 2011, at 15:18, Joe(theWordy)Philbrook jtw...@ttlc.net wrote:
It would appear that on Jul 11, Tom Gundersen did say:
On Mon, Jul 11, 2011 at 7:31 PM, Joe(theWordy)Philbrook jtw...@ttlc.net
wrote:
NOT dual-boot, Multi-boot, And I don't
Am 11.07.2011 17:20, schrieb Joe(theWordy)Philbrook:
Since I multi-boot AND do keep my hardware clock set to local time, I'm a
little bit concerned by this statement. It gives me two questions.
This is no reason. Especially if you dual-boot, keeping the hardware
clock in UTC is something to
On Mon, Jul 11, 2011 at 10:20 AM, Joe(theWordy)Philbrook jtw...@ttlc.netwrote:
It would appear that on 2011-05-02,
www.archlinux.org/news/initscripts-update-1/ did say:
We now strongly discourage the use of HARDWARECLOCK=localtime, as this
may lead to several known and unfixable bugs.
It would appear that on Jul 11, jesse jaara did say:
Check the systemd wiki page it has info for setting windows to UTC time
It's not so much that Windows likes local time. It's that I insist on
it... I MUCH prefer to manually set/verify the hardware clock's time
with the bios set-up
On 11 July 2011 23:20, Joe(theWordy)Philbrook jtw...@ttlc.net wrote:
Since I multi-boot AND do keep my hardware clock set to local time, I'm a
little bit concerned by this statement. It gives me two questions.
I still use localtime and currently I have a dual-boot machine w/
Win7. No problems.
On Mon, Jul 11, 2011 at 7:31 PM, Joe(theWordy)Philbrook jtw...@ttlc.net wrote:
It would appear that on Jul 11, Thomas Bächler did say:
This is no reason. Especially if you dual-boot, keeping the hardware
clock in UTC is something to make your life so much easier.
NOT dual-boot, Multi-boot,
14 matches
Mail list logo
