[gentoo-user] howto get systemd to use localtime (I think)

[gentoo-user] howto get systemd to use localtime (I think)

[covici]

Hi.  I have noticed that when I bootup using systemd, till I run
ntpdate, the times are 4 hours earlier than they should be.  Do I need
an hwclock unit somewhere, or some other command to fix?  I don't think
the clock is actually wrong, its got to have something to do with the
timezone.

Thanks in advance for any suggestions.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

[gentoo-user] Re: howto get systemd to use localtime (I think)

[Jonathan Callen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 05/26/2014 03:44 PM, covici@ccs.covici.com wrote:
> Hi.  I have noticed that when I bootup using systemd, till I run 
> ntpdate, the times are 4 hours earlier than they should be.  Do I
> need an hwclock unit somewhere, or some other command to fix?  I
> don't think the clock is actually wrong, its got to have something
> to do with the timezone.
> 
> Thanks in advance for any suggestions.
> 

First, make sure that the system time zone is correct by making sure
that /etc/localtime is a symlink to your current timezone (in
/usr/share/zoneinfo).

If the only operating system you boot on the machine is Linux (or,
generally, if you *don't* use Windows):

1) Set your BIOS clock to the current time *in UTC*.
2) Ensure that the last line of /etc/adjtime reads "UTC" (instead of
"LOCAL")

If you *do* dual-boot to Windows (and don't want to use the
unsupported methods to make Windows aware that the BIOS time is UTC):

1) Set your BIOS clock to the current *local* time
2) Ensure that the last line of /etc/adjtime reads "LOCAL" (instead of
"UTC").

If you dual-boot Windows 7 or earlier and want to use that unsupported
method mentioned above:

1) Set your BIOS clock to the current time *in UTC*.
2) Ensure that the last line of /etc/adjtime reads "UTC" (instead of
"LOCAL")
3) In Windows, in the registry key
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation"
set the value "RealTimeIsUniversal" (a DWORD if you have to create it)
to "1".

If you use Windows 8, in addition to the above, you have to disable
Windows from ever writing the time to the BIOS clock, otherwise on
shutdown it will reset the BIOS time to local time.

- -- 
Jonathan Callen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJThBBqAAoJELHSF2kinlg4u/sQAIPRMYd5N9CKG9/lZ5MZNWFe
RtFuhTvN3Mrchei3ngIy2Po5dDAZrV0Gbh65aSDnk6s9qbXwpy3HnnlzHnBla6RL
kjaPDlSSPlBziiaEdXUFIj/MEtxTTMGvC9aXbZiQYFyUJS+tnqlpoeSvRgJCRKhf
IT8s9s7xmNePU1jXpNK0LaWJLnpLddb+dqdIRGBLreI0hlMfvjr4qCn41ZfVbARM
E5xLL0jDYRRmeNuzP+fT5FGaSgt9uBlBqlsXFmSZM8tBfImEMlVeG0HfK3qXG5n1
thqx5thth2G2SOkr+m8zUDjcuCIkUSOa5KDslW1k8MX9sN1US9NsPrfT3EqdBuv3
9QoKJMqd8FLUy/gsALM1wt2bbqdaJW9ecEs5kpV4yqwzjtOs21jTaOJQHYLVmhrU
aYvz5BK71iT9dmIn4FuZEhYaCltHnqZwQRzZZEh5U0tdXrfyy9ztenEEEaSeOjxy
B9FVJxo9WbYeBt9iBRJVpT8mwawLseaL229lI2NvM9eB1loIOfyHRtNtVU98mIg9
RsIKW6a4hp0iCPDhxd6OII1B340wtcMo6Dz22TiUoHJaHG0Rkhab+hx/TQnhbCT9
FoVzW20jUsHU10Hg/9VmhYrCI3fZfAH0nqRSV4xsOqRwmZD1E7ff1GXZUx6NVBxg
gc6lh7bpOHZloZC+DU0A
=Ldgh
-----END PGP SIGNATURE-----

Re: [gentoo-user] Re: howto get systemd to use localtime (I think)

[J. Roeleveld]

On Tuesday, May 27, 2014 12:11:22 AM Jonathan Callen wrote:
> On 05/26/2014 03:44 PM, covici@ccs.covici.com wrote:
> If you dual-boot Windows 7 or earlier and want to use that unsupported
> method mentioned above:
> 
> 3) In Windows, in the registry key
> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation"
> set the value "RealTimeIsUniversal" (a DWORD if you have to create it)
> to "1".

That is useful information.
Do you know of any possible side effects from the above setting?

Thanks,

Joost

Re: [gentoo-user] Re: howto get systemd to use localtime (I think)

[covici]

Jonathan Callen <jcallen@gentoo.org> wrote:

> On 05/26/2014 03:44 PM, covici@ccs.covici.com wrote:
> > Hi.  I have noticed that when I bootup using systemd, till I run 
> > ntpdate, the times are 4 hours earlier than they should be.  Do I
> > need an hwclock unit somewhere, or some other command to fix?  I
> > don't think the clock is actually wrong, its got to have something
> > to do with the timezone.
> > 
> > Thanks in advance for any suggestions.
> > 
> 
> First, make sure that the system time zone is correct by making sure
> that /etc/localtime is a symlink to your current timezone (in
> /usr/share/zoneinfo).
> 
> If the only operating system you boot on the machine is Linux (or,
> generally, if you *don't* use Windows):
> 
> 1) Set your BIOS clock to the current time *in UTC*.
> 2) Ensure that the last line of /etc/adjtime reads "UTC" (instead of
> "LOCAL")
> 
> If you *do* dual-boot to Windows (and don't want to use the
> unsupported methods to make Windows aware that the BIOS time is UTC):
> 
> 1) Set your BIOS clock to the current *local* time
> 2) Ensure that the last line of /etc/adjtime reads "LOCAL" (instead of
> "UTC").
> 
> If you dual-boot Windows 7 or earlier and want to use that unsupported
> method mentioned above:
> 
> 1) Set your BIOS clock to the current time *in UTC*.
> 2) Ensure that the last line of /etc/adjtime reads "UTC" (instead of
> "LOCAL")
> 3) In Windows, in the registry key
> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation"
> set the value "RealTimeIsUniversal" (a DWORD if you have to create it)
> to "1".
> 
> If you use Windows 8, in addition to the above, you have to disable
> Windows from ever writing the time to the BIOS clock, otherwise on
> shutdown it will reset the BIOS time to local time.

OK, thanks, I have no /etc/adjtime at all,  and I have two files,
/etc/localtime  (not a link) and /etc/timezone.  Should I delete the
later and change the former to a link?

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] Re: howto get systemd to use localtime (I think)

[wraeth]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 27/05/14 15:37, covici@ccs.covici.com wrote:
> Jonathan Callen <jcallen@gentoo.org> wrote: OK, thanks, I have no
> /etc/adjtime at all,  and I have two files, /etc/localtime  (not a link)
> and /etc/timezone.  Should I delete the later and change the former to a
> link?

What's the output of `timedatectl`?

See http://wiki.gentoo.org/wiki/System_time#systemd
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlOEJzEACgkQXcRKerLZ91kXNwD8CbLIjkD8BZLkUCBzajxSP+na
EDOW7hmeYMqKrC+Vgi0A/06Pe7kb6VQTk2PQ3SPyWExmqvYHlDXo28e0R2QkQyKu
=wzNP
-----END PGP SIGNATURE-----

Re: [gentoo-user] Re: howto get systemd to use localtime (I think)

[covici]

wraeth <wraeth@wraeth.id.au> wrote:

> 
> 
> On 27/05/14 15:37, covici@ccs.covici.com wrote:
> > Jonathan Callen <jcallen@gentoo.org> wrote: OK, thanks, I have no
> > /etc/adjtime at all,  and I have two files, /etc/localtime  (not a link)
> > and /etc/timezone.  Should I delete the later and change the former to a
> > link?
> 
> What's the output of `timedatectl`?
The     output is
      Local time: Tue 2014-05-27 04:46:28 EDT
  Universal time: Tue 2014-05-27 08:46:28 UTC
        RTC time: n/a
       Time zone: n/a (EDT, -0400)
     NTP enabled: no
NTP synchronized: yes
 RTC in local TZ: no
      DST active: yes
 Last DST change: DST began at
                  Sun 2014-03-09 01:59:59 EST
                  Sun 2014-03-09 03:00:00 EDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
                  Sun 2014-11-02 01:59:59 EDT
                  Sun 2014-11-02 01:00:00 EST

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] Re: howto get systemd to use localtime (I think)

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

On Tue, 27 May 2014 01:37:17 -0400, covici@ccs.covici.com wrote:

> OK, thanks, I have no /etc/adjtime at all,  and I have two files,
> /etc/localtime  (not a link) and /etc/timezone.  Should I delete the
> later and change the former to a link?

No. Gentoo copies the correct file from /usr/share/zoneinfo rather than
making a symlink, so that it still works if /usr is a separate filesystem
that has not yet been mounted - the clock is set before local filesystems
are mounted. It uses the contents of /etc/timezone to determine which
file to copy.

Check that /etc/timezone is correct. If not, change it and either copy
the correct file manaually or re-emerge sys-libs/timezone-data.


-- 
Neil Bothwick

Accept that some days you're the pigeon, and some days you're the statue.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: howto get systemd to use localtime (I think)

[covici]

Neil Bothwick <neil@digimed.co.uk> wrote:

> On Tue, 27 May 2014 01:37:17 -0400, covici@ccs.covici.com wrote:
> 
> > OK, thanks, I have no /etc/adjtime at all,  and I have two files,
> > /etc/localtime  (not a link) and /etc/timezone.  Should I delete the
> > later and change the former to a link?
> 
> No. Gentoo copies the correct file from /usr/share/zoneinfo rather than
> making a symlink, so that it still works if /usr is a separate filesystem
> that has not yet been mounted - the clock is set before local filesystems
> are mounted. It uses the contents of /etc/timezone to determine which
> file to copy.
> 
> Check that /etc/timezone is correct. If not, change it and either copy
> the correct file manaually or re-emerge sys-libs/timezone-data.

/etc/timezone is correct.  I wonder when systemd using dracut sets the
time, maybe its confused.  I don't see it using hwclock like openrc used
to, but I found an hwclock unit somewhere, should I try to use that?


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] Re: howto get systemd to use localtime (I think)

[Mike Gilbert]

On Tue, May 27, 2014 at 5:07 AM,  <covici@ccs.covici.com> wrote:
> Neil Bothwick <neil@digimed.co.uk> wrote:
>
>> On Tue, 27 May 2014 01:37:17 -0400, covici@ccs.covici.com wrote:
>>
>> > OK, thanks, I have no /etc/adjtime at all,  and I have two files,
>> > /etc/localtime  (not a link) and /etc/timezone.  Should I delete the
>> > later and change the former to a link?
>>
>> No. Gentoo copies the correct file from /usr/share/zoneinfo rather than
>> making a symlink, so that it still works if /usr is a separate filesystem
>> that has not yet been mounted - the clock is set before local filesystems
>> are mounted. It uses the contents of /etc/timezone to determine which
>> file to copy.
>>
>> Check that /etc/timezone is correct. If not, change it and either copy
>> the correct file manaually or re-emerge sys-libs/timezone-data.
>
> /etc/timezone is correct.  I wonder when systemd using dracut sets the
> time, maybe its confused.  I don't see it using hwclock like openrc used
> to, but I found an hwclock unit somewhere, should I try to use that?
>
>

I believe systemd-timedated should take care of it.

Going back to the /etc/adjtime file that jcallen referred to: You can
create the file and set it to LOCAL by running "timedatectl
set-local-rtc 1".

Re: [gentoo-user] Re: howto get systemd to use localtime (I think)

[covici]

Mike Gilbert <floppym@gentoo.org> wrote:

> On Tue, May 27, 2014 at 5:07 AM,  <covici@ccs.covici.com> wrote:
> > Neil Bothwick <neil@digimed.co.uk> wrote:
> >
> >> On Tue, 27 May 2014 01:37:17 -0400, covici@ccs.covici.com wrote:
> >>
> >> > OK, thanks, I have no /etc/adjtime at all,  and I have two files,
> >> > /etc/localtime  (not a link) and /etc/timezone.  Should I delete the
> >> > later and change the former to a link?
> >>
> >> No. Gentoo copies the correct file from /usr/share/zoneinfo rather than
> >> making a symlink, so that it still works if /usr is a separate filesystem
> >> that has not yet been mounted - the clock is set before local filesystems
> >> are mounted. It uses the contents of /etc/timezone to determine which
> >> file to copy.
> >>
> >> Check that /etc/timezone is correct. If not, change it and either copy
> >> the correct file manaually or re-emerge sys-libs/timezone-data.
> >
> > /etc/timezone is correct.  I wonder when systemd using dracut sets the
> > time, maybe its confused.  I don't see it using hwclock like openrc used
> > to, but I found an hwclock unit somewhere, should I try to use that?
> >
> >
> 
> I believe systemd-timedated should take care of it.
> 
> Going back to the /etc/adjtime file that jcallen referred to: You can
> create the file and set it to LOCAL by running "timedatectl
> set-local-rtc 1".

OK, I will do and see what happens on the next reboot.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

[gentoo-user] Re: howto get systemd to use localtime (I think)

[Jonathan Callen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 05/26/2014 03:44 PM, covici@ccs.covici.com wrote:
> Hi.  I have noticed that when I bootup using systemd, till I run 
> ntpdate, the times are 4 hours earlier than they should be.  Do I 
> need an hwclock unit somewhere, or some other command to fix?  I 
> don't think the clock is actually wrong, its got to have something 
> to do with the timezone.
> 
> Thanks in advance for any suggestions.
> 

First, make sure that the system time zone is correct by making sure
that /etc/localtime is a symlink to your current timezone (in
/usr/share/zoneinfo).

If the only operating system you boot on the machine is Linux (or,
generally, if you *don't* use Windows):

1) Set your BIOS clock to the current time *in UTC*.
2) Ensure that the last line of /etc/adjtime reads "UTC" (instead of
"LOCAL")

If you *do* dual-boot to Windows (and don't want to use the
unsupported methods to make Windows aware that the BIOS time is UTC):

1) Set your BIOS clock to the current *local* time
2) Ensure that the last line of /etc/adjtime reads "LOCAL" (instead of
"UTC").

If you dual-boot Windows 7 or earlier and want to use that unsupported
method mentioned above:

1) Set your BIOS clock to the current time *in UTC*.
2) Ensure that the last line of /etc/adjtime reads "UTC" (instead of
"LOCAL")
3) In Windows, in the registry key
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation"
set the value "RealTimeIsUniversal" (a DWORD if you have to create it)
to "1".

If you use Windows 8, in addition to the above, you have to disable
Windows from ever writing the time to the BIOS clock, otherwise on
shutdown it will reset the BIOS time to local time.

- -- 
Jonathan Callen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJThBXJAAoJELHSF2kinlg4v7sQAK5MEh3dztXxLkEC6LBQjidw
xgNfXdhq5sLGrwx5csN1ORsV29ye61+zQ4R6SfMKlNBlsgMq3Uqpl1Ft5ngGQFYE
hT4dGDdJIF8nPafA/Egov8NYfPk5YWU6jkbMoCuENKGbXx+552IXqg+wBNzRzrl0
avlM5DnUbRQjYQq0M6nhSgX6N0S0bzZ59tXsM1BFy/tjoo+GWpAHW9c3mbuGpG9U
jC3yDhCWq5RlrARrqRWbcuZvaYYe+VBeWW4qXBbSyTbcgXPGiR44lMAYp+LZbxPP
If9yINKweHndOKrcoRVBuXYuGoKIpiTyqXmJEWu7an8SZKKooOV1y3U5vpSlJfmL
MwodtprGvgPLJzCue8OvOBT25/LvH6f6O3j97BuLQb3lL504zEFXYSzj3zDJzCQu
woBtSG4vYKvhuwEHTyTNVf00NKWHjaVhgG5wfkXjZSX3xCl0OAwyf2xExc74gy6m
x5B7l+3ut1Y0x9JsYbVcg4juPnHAz0c16QhlolsTGtfOHj9GBvKhBdn/3lgku0Zi
JfdplxNg9W1gP8eoe1oPfgvaF5gZeLTdOxgFHfNfuF+Pq/hbUNS2dca6O7QonKlL
jOnLSmYgHr6zRha/5J1hADDkHsVYS1d6pVVKBgxwCOkgnboEs8Hxy9Ur6hKFxhbf
OrRwJU2pgq9/J9Wx5+mT
=bqR5
-----END PGP SIGNATURE-----