From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io0-f177.google.com ([209.85.223.177]) by ur; Fri Sep 11 14:13:39 EDT 2015 Received: by ioiz6 with SMTP id z6so106893266ioi.2 for <9front@9front.org>; Fri, 11 Sep 2015 11:13:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=eSMYZ7ZQNR0biEzG5yJgiiEu0sFoMB6lslN3TU7GB2A=; b=GWRdDP0tujI3FfnPImAJdYOXtOZRCbZwi0GeRTl0h5to1SOH8z4xzzQ9TWUmF3nwg3 qUaNfIrYWsiVRkk9cobzxwWJgt6J0yeXbnaaPXbpx8lfkjiJDMXNwbNzCLBmewGfFxgb BSZzcMkMwVFspAlKIAeKKMtuaFZpnFdIReVwPotx8yvbVhTghsUxvY6hD0g/Psxhef27 h4QEC9uwqZzOMp1SD8SQ/WOZzml9QWQq2ejM+eBjm8Y5OYVbcqa+ojFNyBwS9Tvy8YS+ PlRV/kSc6QjQ3ivDiysw/bATc9UFmVjYh9efzFAlCGPnoSksNnhg2XxsIB0G0Y5cOzdG dfrA== MIME-Version: 1.0 X-Received: by 10.107.128.145 with SMTP id k17mr6647654ioi.24.1441995216874; Fri, 11 Sep 2015 11:13:36 -0700 (PDT) Received: by 10.79.93.1 with HTTP; Fri, 11 Sep 2015 11:13:36 -0700 (PDT) Received: by 10.79.93.1 with HTTP; Fri, 11 Sep 2015 11:13:36 -0700 (PDT) In-Reply-To: <7d6350fd91a6668ad5b87afeacc0f5c1@u2.sfldmibb.det.wayport.net> References: <7d6350fd91a6668ad5b87afeacc0f5c1@u2.sfldmibb.det.wayport.net> Date: Fri, 11 Sep 2015 14:13:36 -0400 Message-ID: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: database CSS session-aware generator Subject: Re: [9front] cwfs dump From: Jacob Todd To: 9front@9front.org Content-Type: multipart/alternative; boundary=001a113fbcc6ab736d051f7cac9a --001a113fbcc6ab736d051f7cac9a Content-Type: text/plain; charset=UTF-8 it's hard coded iirc On Sep 11, 2015 2:01 PM, wrote: > 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 > --001a113fbcc6ab736d051f7cac9a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

it's hard coded iirc

On Sep 11, 2015 2:01 PM, <sl@9front.org> wrote:
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
--001a113fbcc6ab736d051f7cac9a-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from u2.inri ([107.191.126.29]) by ur; Fri Sep 11 14:51:43 EDT 2015 Date: Fri, 11 Sep 2015 14:50:57 -0400 From: sl@9front.org To: 9front@9front.org Subject: Re: [9front] cwfs dump Message-ID: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: responsive SQL persistence core engine self-signing generator MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ar.aichi-u.ac.jp ([202.250.160.40]) by ur; Fri Sep 11 19:30:34 EDT 2015 Received: from [192.168.0.249] ([123.1.1.113]) by ar; Sat Sep 12 08:30:22 JST 2015 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: [9front] cwfs dump From: arisawa In-Reply-To: Date: Sat, 12 Sep 2015 08:30:22 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: <83AFDF47-D18D-4506-B6DB-801E419805FD@ar.aichi-u.ac.jp> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: content-addressed secure base descriptor-aware deep-learning GPU generator References: To: 9front@9front.org X-Mailer: Apple Mail (2.2104) the 05:00 is GMT, not local time. inconvenient.=20 Kenji Arisawa > 2015/09/12 3:50=E3=80=81sl@9front.org =E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB= =EF=BC=9A >=20 >> it's hard coded iirc >=20 > 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.* >=20 > * I might not understand what I'm talking about. >=20 > sl From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from felloff.net ([216.126.196.34]) by ur; Fri Sep 11 22:09:26 EDT 2015 Message-ID: <1843000694f353e7801712e0f4348e81@felloff.net> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: base out-scaling storage Date: Sat, 12 Sep 2015 04:09:18 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] cwfs dump In-Reply-To: <83AFDF47-D18D-4506-B6DB-801E419805FD@ar.aichi-u.ac.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ar.aichi-u.ac.jp ([202.250.160.40]) by ur; Sat Sep 12 00:19:25 EDT 2015 Received: from [192.168.0.249] ([123.1.1.113]) by ar; Sat Sep 12 13:19:12 JST 2015 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: [9front] cwfs dump From: arisawa In-Reply-To: <1843000694f353e7801712e0f4348e81@felloff.net> Date: Sat, 12 Sep 2015 13:19:12 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: <5987D4F9-71FF-4B26-851E-B35428C6AF73@ar.aichi-u.ac.jp> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: lossless polling control References: <1843000694f353e7801712e0f4348e81@felloff.net> To: 9front@9front.org X-Mailer: Apple Mail (2.2104) Thanks > 2015/09/12 11:09=E3=80=81cinap_lenrek@felloff.net =E3=81=AE=E3=83=A1=E3=83= =BC=E3=83=AB=EF=BC=9A >=20 > 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. >=20 > 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. >=20 > 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. >=20 > -- > cinap