On Sat, Jan 24, 2004 at 10:07:40AM +0100, Marek Zachara wrote:
> I have managed to get through the installation and configuration
> of both coda client and server 'grepping' the mailing lists and documentation
> but now I have come across weird problem...
...
> and the SrvLog at coda server (host1) says:
> 09:52:37 CheckSetACLSemantics: rights violation (9 : 9) (10000001.1.1)
> 09:52:37 Entering VFlushVnode for vnode 0x1

According to this your admin used only has read and lookup rights. The
only way I can see this happen is when the client failed to tear down
all the old connections to the server and it is as far as the server is
concerned still using an anonymous connection.

The other possibility could be that user-id 17 was only added to the
System:Administrators group after the authenticated connection was set
up. Although that isn't really all that likely either considering that
you did successfully make modifications a day earlier.


On Sun, Jan 25, 2004 at 09:25:32AM +0100, Marek Zachara wrote:
> Hmm, I have solved the problem, but still don't know what was causing
> it... 

Restarting/reinitializing a client can fix a lot of subtle problems.
Any previously existing connections are gone, so when you clog the
client will have to build a new connection and will definitely use the
information from the Coda token. Also because reinit kills off all
cached objects, there can't be any version skew resulting from an
operation that the client did in a different way compared to the server
which would be invisible if the version vectors are identical and only
get resolved when the client drops the cached object.

Jan