On Tuesday, November 11, 2014 3:16:19 pm Charles Swiger wrote:
> On Nov 11, 2014, at 10:57 AM, John Baldwin wrote:
> > On Monday, November 10, 2014 7:36:19 am Lev Serebryakov wrote:
> >>
> >> After changing timezones in Russia (with replacing /etc/localtime
> >> with new file), I found that cron
On Tue, Nov 11, 2014, at 13:16, Dimitry Andric wrote:
> On 11 Nov 2014, at 04: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"
On Nov 11, 2014, at 10:57 AM, John Baldwin wrote:
> On Monday, November 10, 2014 7:36:19 am 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 sa
On Tue, Nov 11, 2014 at 01:57:40PM -0500, John Baldwin wrote:
> On Monday, November 10, 2014 7:36:19 am 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 se
On Monday, November 10, 2014 7:36:19 am 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
On 11 Nov 2014, at 04: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 cr
On Nov 11, 2014, at 00:56, David Chisnall wrote:
>
> On 11 Nov 2014, at 03:35, Allan Jude wrote:
>
>> 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 const
On 11 Nov 2014, at 03:35, Allan Jude wrote:
> 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.
Darwin also has the notify(3) interface, which allow
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
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 r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
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 onc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
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 onc
12 matches
Mail list logo
