[systemd-devel] Problem with systemd-timedated

Kay Sievers kay at vrfy.org
Sat Oct 27 07:29:43 PDT 2012


On Sat, Oct 27, 2012 at 4:20 PM, Maciej Piechotka <uzytkownik2 at gmail.com> wrote:
> On Sat, 2012-10-27 at 13:53 +0200, Kay Sievers wrote:
>> On Sat, Oct 27, 2012 at 12:37 PM, Maciej Piechotka
>> <uzytkownik2 at gmail.com> wrote:
>> > After some update of systemd the systemd-timedated stopped starting
>> > automatically which causes troubles for timezone settings. I cannot find
>> > anything in logs. When I run it by hand everything works.
>>
>> What kind of trouble?
>>
>
> TZ is not set. I can manually issue:

You mean glibc's timezone is not set, the kernel's timezone is not
set, or the environment variable TZ?

> # ln -sf /usr/share/zoneinfo/Europe/London /etc/localtime
>
> or
>
> # cp /usr/share/zoneinfo/Europe/London /etc/localtime

Not sure I understand that,

I don't think it has much to do with timedated. It is not supposed to
run at bootup, it is only a "mechanism" that starts when tools call
it. Nothing during bootup should do that.

/etc/localtime is a static configuration which should always be on
disk when the machine has a local timezone, and it should never be
touched at bootup. And it should always be a symlink.

Kay


More information about the systemd-devel mailing list