I haven't been able to write a single file in Coda since
July 19, when I reported the problems I've had to this list
after 'upgrading' to 5.3.8.  After the release of 2.2.17 I
tried recompiling everything.  Still no luck.

Jan Harkes wrote:
>On Wed, Jul 19, 2000 at 10:44:28PM +0100, Dr A V Le Blanc wrote:
>> On Thu, Jul 20, 2000 at 11:40:38AM -0400, Jan Harkes wrote:
>>> Is any activity in codacon indicating that venus tries to send a
>>> Create/Store to the server.
>> 
>> Here is 'cp /etc/passwd .;rm passwd':
>> 
>>      Create passwd ( 23:10:23 )
>>      Store passwd [0] ( 23:10:23 )
>
>This indicates that when Venus receives the close upcall, the container-
>file is zero length. I'll have to look whether some changes were made in
>2.2.16 that are causing this.

Surely if there are problems others should see them.  I do have problems
on 2.2.15, 16, and now 17.  I suppose not many people are using
KTH kerberos 5 (heimdal) with coda, but that shouldn't affect
anything after I get my ctoken, should it?

I wrote:
> $ strace -e trace=file cp -p /etc/passwd .
> execve("/bin/cp", ["cp", "-p", "/etc/passwd", "."], [/* 20 vars */]) = 0
> open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or directory)
> open("/etc/ld.so.cache", O_RDONLY)      = 3
> open("/lib/libc.so.6", O_RDONLY)        = 3
> lstat(".", {st_mode=S_IFDIR|0711, st_size=2048, ...}) = 0
> stat(".", {st_mode=S_IFDIR|0711, st_size=2048, ...}) = 0
> stat("/etc/passwd", {st_mode=S_IFREG|0644, st_size=1104, ...}) = 0
> stat("./passwd", 0xbffff7dc)            = -1 ENOENT (No such file or directory)
> open("/etc/passwd", O_RDONLY|0x8000)    = 3
> open("./passwd", O_WRONLY|O_CREAT|O_TRUNC|0x8000, 0600) = 4
> utime("./passwd", [2000/07/20-23:10:23, 2000/07/19-00:01:34]) = 0
> chown("./passwd", 102, 0)               = 0
> chmod("./passwd", 0100644)              = 0
> $

And Jan wrote:
> Didn't see any of the read/write/close calls here, I figured that the
> open() or close() calls would be failing, but from this trace it looks
> like nothing is wrong.

Is anyone else seeing problems with writing data using Coda 5.3.8?

     -- Owen
     LeBlanc_at_mcc.ac.uk