* Re: [9front] cwfs dump
@ 2015-09-11 18:50 sl
2015-09-11 23:30 ` arisawa
0 siblings, 1 reply; 5+ messages in thread
From: sl @ 2015-09-11 18:50 UTC (permalink / raw)
To: 9front
> it's hard coded iirc
All documentation claims it is hardcoded for 05:00. I'm asking
why it (seems to) ignore the OS time in favor of the time inherited
from the BIOS.*
* I might not understand what I'm talking about.
sl
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] cwfs dump
2015-09-11 18:50 [9front] cwfs dump sl
@ 2015-09-11 23:30 ` arisawa
2015-09-12 2:09 ` cinap_lenrek
0 siblings, 1 reply; 5+ messages in thread
From: arisawa @ 2015-09-11 23:30 UTC (permalink / raw)
To: 9front
the 05:00 is GMT, not local time.
inconvenient.
Kenji Arisawa
> 2015/09/12 3:50、sl@9front.org のメール：
>
>> it's hard coded iirc
>
> All documentation claims it is hardcoded for 05:00. I'm asking
> why it (seems to) ignore the OS time in favor of the time inherited
> from the BIOS.*
>
> * I might not understand what I'm talking about.
>
> sl
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] cwfs dump
2015-09-11 23:30 ` arisawa
@ 2015-09-12 2:09 ` cinap_lenrek
2015-09-12 4:19 ` arisawa
0 siblings, 1 reply; 5+ messages in thread
From: cinap_lenrek @ 2015-09-12 2:09 UTC (permalink / raw)
To: 9front
correct. cwfs uses the systems time, which is initialized to from
rtc by /boot/boot (to get at least the date right), but is later
corrected by aux/timesync once the system is fully booted up.
the problem was that cwfs didnt use the local timezone because
/env/timezone is missing on boot.
i just pushed a change that makes cwfs read in /adm/timezone/local
when /env/timezone is missing so dump times will be in local time
now.
this was a classical bootstrap problem. normally, /env/timezone is
initialized by /bin/init, but cwfs is not run after init because
because init is on the very filesystem cwfs serves.
--
cinap
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] cwfs dump
2015-09-12 2:09 ` cinap_lenrek
@ 2015-09-12 4:19 ` arisawa
0 siblings, 0 replies; 5+ messages in thread
From: arisawa @ 2015-09-12 4:19 UTC (permalink / raw)
To: 9front
Thanks
> 2015/09/12 11:09、cinap_lenrek@felloff.net のメール：
>
> correct. cwfs uses the systems time, which is initialized to from
> rtc by /boot/boot (to get at least the date right), but is later
> corrected by aux/timesync once the system is fully booted up.
> the problem was that cwfs didnt use the local timezone because
> /env/timezone is missing on boot.
>
> i just pushed a change that makes cwfs read in /adm/timezone/local
> when /env/timezone is missing so dump times will be in local time
> now.
>
> this was a classical bootstrap problem. normally, /env/timezone is
> initialized by /bin/init, but cwfs is not run after init because
> because init is on the very filesystem cwfs serves.
>
> --
> cinap
^ permalink raw reply [flat|nested] 5+ messages in thread
* cwfs dump
@ 2015-09-11 18:00 sl
2015-09-11 18:13 ` [9front] " Jacob Todd
0 siblings, 1 reply; 5+ messages in thread
From: sl @ 2015-09-11 18:00 UTC (permalink / raw)
To: 9front
Why does cwfs dump not use the system time?
Example:
My file server is set to U.S. Eastern Time, and the dump triggers
early every morning at 01:00.
sl
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-09-12 4:19 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-11 18:50 [9front] cwfs dump sl
2015-09-11 23:30 ` arisawa
2015-09-12 2:09 ` cinap_lenrek
2015-09-12 4:19 ` arisawa
-- strict thread matches above, loose matches on Subject: below --
2015-09-11 18:00 sl
2015-09-11 18:13 ` [9front] " Jacob Todd
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).