From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 22 Feb 2015 15:31:38 -0600 Message-ID: From: Steven Stallion To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c30240be14e1050fb40200 Subject: Re: [9fans] Odd dirwstat behavior Topicbox-Message-UUID: 4584c926-ead9-11e9-9d60-3106f5b1d025 --001a11c30240be14e1050fb40200 Content-Type: text/plain; charset=UTF-8 On Sun, Feb 22, 2015 at 2:53 PM, Steven Stallion wrote: > 9fans, > > Somewhat recently I've been doing some work to preserve older fs > hierarchies. When running replica/pull I'm seeing something quite strange. > Both the log and database are reporting the original (and correct) mtime > for directories, however for some reason replica/applylog (or the > filesystem) is setting the mtime to time(0). After digging through the > applylog source, I found a couple of conditions that could cause this, > however my modifications have been for naught. This is annoying as hell > given the fact I'm going through this rigamarole to preserve permissions > and dates. > > FWIW, replica/applylog is running against a fossil filesystem served out > of devmnt with the following configuration: > > fsys main config > fsys main open -APVW > > Any ideas? > Ugh. I see the problem - a second pass is not made by applylog to update the mtime after files have been applied. Patch forthcoming. Steve --001a11c30240be14e1050fb40200 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On S= un, Feb 22, 2015 at 2:53 PM, Steven Stallion <sstallion@gmail.com&g= t; wrote:
9fans,<= div>
Somewhat recently I've been doing some work to prese= rve older fs hierarchies. When running replica/pull I'm seeing somethin= g quite strange. Both the log and database are reporting the original (and = correct) mtime for directories, however for some reason replica/applylog (o= r the filesystem) is setting the mtime to time(0). After digging through th= e applylog source, I found a couple of conditions that could cause this, ho= wever my modifications have been for naught. This is annoying as hell given= the fact I'm going through this rigamarole to preserve permissions and= dates.

FWIW, replica/applylog is running against = a fossil filesystem served out of devmnt with the following configuration:<= /div>

fsys main config
fsys main open -APVW

Any ideas?

Ugh. I see the problem - a second pass is not made by applylog to update= the mtime after files have been applied. Patch forthcoming.

=
Steve=C2=A0
--001a11c30240be14e1050fb40200--