Coda File System

RVM size + authentication

From: Peter Schüller <>
Date: Fri, 1 Jun 2001 12:46:59 +0200
Hash: SHA1


I've been aware of Coda for a while now, and now I've begun to consider using 
it (after reading some more of the docs, it appears it's in a much more 
stable state than I first thought).

There are two things that are bothering me however:

(1) RVM size.

Suppose we want 100 GB of data on a server. Using the 4% approximation, 
that's more than 4 gig of RVM. This poses a problem because RVM is mapped to 
virtual memory (I'm talking 32 bit architectures now). How is this problem 
usually solved?

Also, do we actually need that much physical RAM to achieve high performance, 
or is RVM expected to be mostly accessed on disk? I realize all the data is 
mapped, but I mean in terms of cache:ing the data in RAM.

(2) How is user authentication handled in a server environment? That is, 
assuming the Coda clients are servers with long-running processes. The 
daemons need to be able to access the Coda file system. Given that 
authentication tickes expire, how is this done?

And also, is there a PAM module available? If not, how do you solve the 
problem inherent to having user home directories on Coda (i.e. the user 
cannot immediately access his/her home directory after logging in)? Having 
the user first log in, having access to nothing, and then log into coda 
(second step) is somewhat "ugly" in my opinion.

I'm looking to set up an LDAP + Coda style system with everything centralized 
and dumb "pluggable" servers. With OpenAFS I can use kerberos for 
authentication, for which there are PAM modules. Is there a similar solution 
for Coda?

- -- 
/ Peter Schuller, InfiDyne Technologies HB

PGP userID: 0xE9758B7D or 'Peter Schuller <>'
Key retrival: Send an E-Mail to
E-Mail: Web:

Version: GnuPG v1.0.5 (GNU/Linux)
Comment: For info see

Received on 2001-06-01 06:50:07