On 11 Nov 2014, at 04:28, Mark Felder <f...@freebsd.org> wrote:
> On Mon, Nov 10, 2014, at 06:36, Lev Serebryakov wrote:
>> After changing timezones in Russia (with replacing /etc/localtime
>> with new file), I found that cron works in "old" timezone till
>> restart. And all other services do the same, but cron is most obvious
>> here :)
>> Looks like libc reads timezone only once and it could not be chamged
>> for process without restart (which leads to, effectivly, restart of
>> whole server).
>> Is it known problem? I think, it should be fixed somehow. I
>> understand, that re-check timezone file on each time-related call
>> could be expensive, though :(
> I think this was one of the crowning achievements of systemd, but I'm
> sure someone can come up with something much more sane than that to
> address this problem.

Actually, it isn't:

This reads "Note that this service will not inform you about system time
changes. Use timerfd() with CLOCK_REALTIME and TFD_TIMER_CANCEL_ON_SET
for that."

So it mostly looks like a shared service to provide the graphical time
control panel for GNOME.


Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to