Re: [9fans] /dist is empty

[Russ Cox <rsc@plan9.bell-labs.com>]

Matthias Teege wrote:

>rsc@plan9.bell-labs.com (Russ Cox) writes:
>
>
>
>>to mount the cd and then replica/pull -v script
>>where script is an edited copy of
>>/dist/replica/cd.
>>
>>
>
>I solved my CD problem, transfer the plan9.iso to the cpu/auth
>server and mount it via "mount /srv/9660 /n/dist
>/usr/bootes/plan9.iso". After that I read man 1 replica and the
>"cd" script but I didnt get it.
>
>I mount the fileserver via "9fs batida" to /n/batida and change the
>"cd" script on the cpu/auth server like that:
>
>s=/n/dist/dist/replica
>serverroot=/n/dist
>serverlog=/dist/replica/plan9.log
>serverproto=$s/plan9.proto
>fn servermount { status='' }
>fn serverupdate { status='' }
>
>fn clientmount { status='' }
>c=/dist/replica
>clientroot=/n/batida
>clientproto=$c/plan9.proto
>clientdb=$c/client/plan9.db
>clientexclude=(dist/replica/client)
>clientlog=$c/client/plan9.log
>
>applyopt=(-u -T$c/client/plan9.time)
>
>replica/pull -v script runs without error (after touching
>/dist/replica/plan9.log) but there are no files transfered to the
>fileserver.
>
>What do I missing?
>
>

i'm not sure exactly, but i bet you should be setting
c=/n/batida/dist/replica.
as it is, it's using your local machines /dist database to decide
how to handle /n/batida.  if your local machine is up-to-date
then no copying is going to happen on /n/batida.