[9fans] replica/pull problem with antiword

[9fans] replica/pull problem with antiword

[kazumi iwane]

Hello 9fans,

I am having a problem with replica/pull. When I do:

  term% replica/pull -vs /dist/replica/network sys/src/cmd/aux/antiword

it updates permission of sys/src/cmd/aux/antiword/* to 640, then to 660,
and then to 664. And this 640-660-664 dance repeats again and again
each time I do the pull.

Is this just me? Is anything wrong with my plan9.db or plan9.log?
--
- kazumi

Re: [9fans] replica/pull problem with antiword

[geoff]

It's not just you.  I grep out the antiword noise in my `pull' wrapper:

#!/bin/rc
# pull - pull system files from 1127
rfork e
opts=()
done=0
while (~ $done 0 && test $#* -gt 0 && ~ $1 -*) {
	switch ($1) {
	case -[cns];	opts=($opts $1)
	case --;	done = 1		# no break in rc, alas
	case -*
		echo usage: $0 '[-cns][file]...' >[1=2]
		exit usage
	}
	shift
}

9fs boot
9fs sources
if (test ! -e /n/sources/plan9) {
	rm -f /srv/sources
	9fs sources
}
if (test ! -e /n/sources/plan9) {
	rm -f /srv/sources
	echo $0: sources did not mount >[1=2]
	exit no-sources
}

label 'rc pull' >[2]/dev/null
replica/pull -v $opts /dist/replica/network $* >[2=1]  |
	tee $home/pull/log |
	grep -v ' locally created
 metadata locally changed
 will not remove
^sys/lib/fax/
^lib/face/.*contents locally modified; will not update metadata
^sys/src/9/pc/pc.*: locally modified; will not update
^m .*antiword|^(. )?(386/9.*|adm/.*|dist/replica/network|lib/face/48x48x./\.dict|mail/lib/ignore|rc/bin/.*rc|sys/lib/man/lookman/index|sys/log/.*|sys/man/[0-9]/INDEX.*|sys/src/9/boot/libboot\.a.)($|[: ])'

Re: [9fans] replica/pull problem with antiword

[Russ Cox]

> Hello 9fans,
> 
> I am having a problem with replica/pull.  When I do:
> 
>   term% replica/pull -vs /dist/replica/network
>   sys/src/cmd/aux/antiword
> 
> it updates permission of sys/src/cmd/aux/antiword/* to 640, then to 660,
> and then to 664.  And this 640-660-664 dance repeats again and again
> each time I do the pull.

Could you send me the whole output of the command?

The fact that pull is reprocessing that section of log means
that it thinks that part of the log has not been applied.
It always starts at the beginning of the first section of log
that hasn't been applied and processes from there to the end.
As time goes on, pull will get slower and slower, as there will
be more log to process.  This is an error worth fixing.

Russ

Re: [9fans] replica/pull problem with antiword

[kazumi iwane]

[-- Attachment #1: Type: text/plain, Size: 294 bytes --]

On 1/28/06, Russ Cox <rsc@swtch.com> wrote:
> Could you send me the whole output of the command?

Gladly. Gzip'd output is attached.

By the way, without -s option, replica/pull produces whole series of
"contents locally modified; will not update metdata to ..." messages.
--
- kazumi

[-- Attachment #2.1: Type: text/plain, Size: 345 bytes --]

from postmaster@ethel:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/x-gzip; name=pull.out.gz
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment; filename="pull.out.gz"

[-- Attachment #2.2: pull.out.gz.suspect --]
[-- Type: application/octet-stream, Size: 1028 bytes --]

Re: [9fans] replica/pull problem with antiword

[Charles Forsyth]

[-- Attachment #1: Type: text/plain, Size: 379 bytes --]

somewhere in the archives there should be an old discussion of
some of this with the actions required to get it to stop
producing the diagnostics.  i think it might have been antiword causing the
trouble at the time, and that it's a result of changes to metadata.
i've now forgotten the details, so i'd need to work it out again,
but i might have said something at the time.

[-- Attachment #2: Type: message/rfc822, Size: 3109 bytes --]

From: "Russ Cox" <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] replica/pull problem with antiword
Date: Sat, 28 Jan 2006 09:22:20 -0500
Message-ID: <20060128142225.3F4031E8C29@holo.morphisms.net>

> Hello 9fans,
> 
> I am having a problem with replica/pull.  When I do:
> 
>   term% replica/pull -vs /dist/replica/network
>   sys/src/cmd/aux/antiword
> 
> it updates permission of sys/src/cmd/aux/antiword/* to 640, then to 660,
> and then to 664.  And this 640-660-664 dance repeats again and again
> each time I do the pull.

Could you send me the whole output of the command?

The fact that pull is reprocessing that section of log means
that it thinks that part of the log has not been applied.
It always starts at the beginning of the first section of log
that hasn't been applied and processes from there to the end.
As time goes on, pull will get slower and slower, as there will
be more log to process.  This is an error worth fixing.

Russ

Re: [9fans] replica/pull problem with antiword

[kazumi iwane]

On 1/29/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> somewhere in the archives there should be an old discussion of
> some of this with the actions required to get it to stop
> producing the diagnostics.  i think it might have been antiword causing the
> trouble at the time, and that it's a result of changes to metadata.
> i've now forgotten the details, so i'd need to work it out again,
> but i might have said something at the time.

You are right; it was antiword, it was metadata, and you did say
(many!) things.

http://groups.google.com/group/comp.os.plan9/browse_thread/thread/158a2414a4678ae2/d68e2cac4fcf4d2c?tvc=2&q=group%3Acomp.os.plan9+antiword#d68e2cac4fcf4d2c
--
- kazumi