* Re: [9fans] replica problems
@ 2002-05-14 15:53 Russ Cox
0 siblings, 0 replies; 4+ messages in thread
From: Russ Cox @ 2002-05-14 15:53 UTC (permalink / raw)
To: 9fans
Right, the file didn't exist because you didn't
copy it. It gets handled like any other file, except
that it's needed to run replica/push.
Until you pull it down, pushes should
fail. They should not, however, just remove
files from the server.
Russ
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9fans] replica problems
@ 2002-05-14 7:52 Fco.J.Ballesteros
0 siblings, 0 replies; 4+ messages in thread
From: Fco.J.Ballesteros @ 2002-05-14 7:52 UTC (permalink / raw)
To: 9fans
[-- Attachment #1: Type: text/plain, Size: 100 bytes --]
The file did not exist. I'll try again
a couple of times to see if I understand
what's going on.
[-- Attachment #2: Type: message/rfc822, Size: 1735 bytes --]
From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica problems
Date: Mon, 13 May 2002 12:57:00 -0400
Message-ID: <667d1ef0052669658ece75b48f079efb@plan9.bell-labs.com>
Uhh... That should not have happened.
Does /usr/nemo/lib/replica/nemo.proto
exist on your laptop? I think the problem is that
the proto file couldn't be opened, so the view of
the local fs through the proto was absolutely
no files, meaning you deleted your bin/* files.
So the delete propagated.
Still, revrdproto looks like it should be returning -1
when the proto doesn't exist, which should cause
applychanges to exit immediately.
Russ
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9fans] replica problems
@ 2002-05-13 16:57 rsc
0 siblings, 0 replies; 4+ messages in thread
From: rsc @ 2002-05-13 16:57 UTC (permalink / raw)
To: 9fans
Uhh... That should not have happened.
Does /usr/nemo/lib/replica/nemo.proto
exist on your laptop? I think the problem is that
the proto file couldn't be opened, so the view of
the local fs through the proto was absolutely
no files, meaning you deleted your bin/* files.
So the delete propagated.
Still, revrdproto looks like it should be returning -1
when the proto doesn't exist, which should cause
applychanges to exit immediately.
Russ
^ permalink raw reply [flat|nested] 4+ messages in thread
* [9fans] replica problems
@ 2002-05-13 15:48 Fco.J.Ballesteros
0 siblings, 0 replies; 4+ messages in thread
From: Fco.J.Ballesteros @ 2002-05-13 15:48 UTC (permalink / raw)
To: 9fans
Hi,
Is anyone out there using replica to sync a home
directory between the file server and a laptop's kfs?
I tried several times to do it and failed.
To do it `the right way' (or what I thought it was such),
I removed /usr/nemo on my laptop; then created an empty one;
then defined the replica config file
shown below to replicate the file server's /usr/nemo on my laptop.
I executed
replica/scan /path/to/config
replica/pull /path/to/config bin
and brought my $home/bin back to my laptop. fine.
but, when I executed
replica/push /path/to/config bin
it deleted all the $/home/bin files from the server (they were not
deleted from the client, but the db said so).
AFAIK, replica/push should have done nothing, right?
What am I doing wrong?
This was the config file:
# replica(1) file to be run at nautilus
fn servermount { bind -c /n/sargazos/usr/nemo /n/dist }
fn serverupdate { status='' }
# Sargazos /usr/nemo
serverroot=/n/dist
s=/n/dist/lib/replica
serverlog=$s/nemo.log
serverproto=$s/nemo.proto
proto=$serverproto
serverdb=$s/nemo.db
# laptop /usr/nemo
fn clientmount { test -d /usr/nemo }
clientroot=/usr/nemo
c=/usr/nemo/lib/replica
clientlog=$c/nautilus/nemo.log
clientproto=$c/nemo.proto
clientdb=$c/nautilus/nemo.db
clientexclude=(lib/replica/nautilus offline tmp)
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-05-14 15:53 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-05-14 15:53 [9fans] replica problems Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2002-05-14 7:52 Fco.J.Ballesteros
2002-05-13 16:57 rsc
2002-05-13 15:48 Fco.J.Ballesteros
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).