On Mon, Jul 09, 2001 at 09:29:05PM +0200, Peter Schuller wrote:
> Hello,
> 
> I finally got a chance to set up a coda server separate from my coda client.
> One of the things I noticed was that doing an "ls" in /coda yieled incorrect
> owner usernames. At first I thought, sure, it's because it's using the
> server's user ID which doesn't correspond to my local ids.

Correct we don't map Coda user-ids in the filesystem to local userids.

> But then I noticed that the coda id was 1000, the local id was 1003 (output
> of ctokens), BUT the id that showed up as ownder of the files was 1004!
> 
> Where did 1004 come from?

I'm not sure, but sometimes the lack of uid mapping makes the 'owner' of
a file a bit funny. Still, Coda ignores the unix permissions and owner
information and relies purely on the directory ACL for access
permissions so a funny userid shouldn't affect normal operation.

Say I have local userid 500, but my Coda id is 7000. When I initially
create a file it's uid will show up as 500, however on the server the
owner will already be 7000. Once the object is removed from the cache,
or revalidated, and refetched from the server, the id should show up
as 7000 on the client.

There is one exception, people who have admin rights (by being member of
the System:Administrators group) can actually use chown. Tar and cp tend
to use chown to preserve file attributes. Maybe the file was originally
owned by user id 1004 on the local system?

Jan