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.
--- Begin Message ---> 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
--- End Message ---
