On 2014-11-10 22:28, Mark Felder 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. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" >
jkh@ mentioned this specifically when he gave his talk at EuroBSDCon and MeetBSD, about how Apple solved this in LaunchD, because apparently originally libc DID check /etc/localtime constantly. -- Allan Jude
signature.asc
Description: OpenPGP digital signature
