RE: and yet muddier

Subject: RE: and yet muddier
From: Chris Herrmann (chris@faredge.com.au)
Date: Mon Jul 09 2001 - 20:38:43 EDT

Thanks Thomas, will try later today. The problems weren't solved by what I
tried last night - they only appear when several people are using the
server, however, over an hour or so. Some other strange behaviour - first
person on can use network trash, but noone else can.

Grr!

Is anyone able to explain why I should/shouldn't use

--enable-lastdid

and

--with-flock-locks

The documentation didn't provide many clues as to why you would choose to
use them. Also, as I'm running it on a Redhat System, should I use:

--enable-redhat

?

Many thanks,

Chris

-----Original Message-----
From: Thomas Schierle [mailto:ts@visual-s.de]
Sent: Monday, 9 July 2001 23:11
To: Netatalk-Admins
Subject: Re: and yet muddier

On 01-07-09 12:27 +0200, Chris Herrmann wrote:

> If i remove all semblances of security, and load only uams_guest.so, and
get
> everyone to connect as guest, then 1 of the users can use the network
trash,
> and all of them appear to be saving ok / using quark ok...

Chris, try to compile with --enable-dropkludge, IMO that's
an essential if you want to work off your netatalk server with
QuarkXPress.

btw, I don't remember the details anymore -- but I have better luck
with byte range locking instead of flock-locks.

hth, -Thomas 

--
Thomas Schierle, Munich, Germany

PGP key [DSS/DH] 0xA23CDA1D available at various public key servers

This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:44 EDT