On: Thu, 14 Feb 2002 17:47:09 -0500,
Jan Harkes <[EMAIL PROTECTED]> wrote:
[...]
> Cool, thanks for finding this one, I mostly test the build of the
> 'rpm/debian packaged' version of Coda where everything is found in the
> default paths, so these are the typical kinds of problems that pop up.
On Thu, Feb 14, 2002 at 10:49:45PM +0100, Rene Rebe wrote:
> So I took a look into the source:
> echo
> echo "Rdsinit will initialize data and log."
> echo "This takes a while."
> -f $log $data $parms
>
> Ok. The error is obvious. In the original archive you have this:
> @RDSINIT
Hi all.
I just started to test CODA for Laptop syncronization using the
disconnected functionallity.
But I just get into problem in the beginning, setting the server
up. (Test system only - no production systems involved ;-).
As read in the "CODA manual" I executed vice-setup and an
On Mon, May 21, 2001 at 12:52:44PM -0500, Kelly Corbin wrote:
> I found the problem. updatesrv when called from codastart has the -p
> /vice/db option which sets the working directory as /vice/db. When the
> vice-setup script is run on the non-scm machine and calls updatefetch,
&
I found the problem. updatesrv when called from codastart has the -p
/vice/db option which sets the working directory as /vice/db. When the
vice-setup script is run on the non-scm machine and calls updatefetch,
it looks for $vicedir/db/servers which is actually /vice/db/db/servers
(it
tried to run vice-setup from scratch with the same error
message.
What gives?
There seems to be no good way to debug this. What file is it looking
for? If I look at the script, the line called is:
updatefetch -h $scmhost -r db/servers -l servers ;
which would mean that it's trying to fetc
Hi,
I recently installed a new coda SCM server on FreeBSD 4.2. This has all
gone well as to the instructions. However when I try to build the
non-scm server, vice-setup stops with the following message :
Fetch failed with No such file or directory
updatefetch failed with No such file or
According to Brad Clements:
>
>vice-setup-rvm is the closest script I can find. It doesn't call uname.
>
Mmmm bummer - I have seen that message when my the case statement did
not recognnise my machine and left the shared memory parameters at the
default, the shared memory segment c
ion. Unfortunately I think things have changed for
this release.
vice-setup-rvm is the closest script I can find. It doesn't call uname.
In fact, none of the vice-setup scripts call uname other than vice-setup,
which appears to be looking for BSD only just to setup init for reboot.
It
According to Brad Clements:
>
>I'm using raw partitions for rvm log and data on RH 7.. any ideas?
>
I _think_ the script is called rvm_setup (I do not have access to my
server to check). In there there is a case statement just after a
uname. Check that the output of your uname matches one of th
nd or fix the problems and rerun /usr/sbin/vice-setup.
[root@eiger]#
Brad Clements,[EMAIL PROTECTED] (315)268-1000
http://www.murkworks.com (315)268-9812 Fax
netmeeting: ils://ils.murkworks.com AOL-IM: BKClements
On Wed, Jan 10, 2001 at 06:50:26PM +, [EMAIL PROTECTED] wrote:
> I'm planning on dipping my toe into the coda waters with a file system
> of around 34 GB. Since this isn't one of the options supported by
> vice-setup-rvm I thought I would just hack the script by taking the
>I'm planning on dipping my toe into the coda waters with a file system
>of around 34 GB. Since this isn't one of the options supported by
>vice-setup-rvm I thought I would just hack the script by taking the
>3.3 GB option and just multiplying everything by 10.
Read the
I'm planning on dipping my toe into the coda waters with a file system
of around 34 GB. Since this isn't one of the options supported by
vice-setup-rvm I thought I would just hack the script by taking the
3.3 GB option and just multiplying everything by 10.
Is this sensible or are
I am getting an error at the end of vice-setup.
this is configuring on the CSM just after it creaates the log and data
partitions
LOG file has been initialized!
Rdsinit will initialize data and log.
This takes a while.
rvm_initialize succeeded.
Going to initialize data file to zero, could
On Fri, Feb 25, 2000 at 10:10:11AM +0100, Nicolas Maillot wrote:
> Hi,
>
> thank you very much for helping me so quickly...
> but as you can see here on the mount command output , /dev/hda9 is mounted
> on /vicepa
> ... I still don't understand why the partition is not found
I'm just looking t
gt; > First of all, i'd like to say that coda seems to have very nice
> features..
> > I can't wait trying them.
> >
> > But I've got a problem during vice-setup ... I get a strange message
> > during the server directory configuration
> >
&g
On Thu, Feb 24, 2000 at 12:17:00PM +0100, Nicolas Maillot wrote:
> Hi ,
>
> First of all, i'd like to say that coda seems to have very nice features..
> I can't wait trying them.
>
> But I've got a problem during vice-setup ... I get a strange mess
Hi ,
First of all, i'd like to say that coda seems to have very nice features..
I can't wait trying them.
But I've got a problem during vice-setup ... I get a strange message during the
server directory configuration
(everything goes all right before this.
I've cre
On Wed, Jan 19, 2000 at 03:39:56PM -0800, Tom Tarka wrote:
> is there a way to specify multiple storage areas for the root volume
> in vice-setup.
>
> i.e.
>
> i have /vicepa and /vicepb on different partitions and when
> vice setup asks where I want my root volume, I
is there a way to specify multiple storage areas for the root volume
in vice-setup.
i.e.
i have /vicepa and /vicepb on different partitions and when
vice setup asks where I want my root volume, I'd like it to
span both.
Should I just do this later, and if so, how? I thought about
do
21 matches
Mail list logo
