On Thu, Jun 08, 2000 at 01:50:41PM +0200, Hauke Fath wrote:
> "Harm" is not the point. The combination of Netatalk and various MacOS
> versions is not exactly quirk-free; and wasting time digging through
> several source trees for the origin of kewl&lazy error messages /
> diagnostics can be pretty annoying. 
> 
> Having given battle to pap/psf while getting them to work with an oldish
> QMS printer, I am all with Eric here.
> 
> > This seems to happen when there's an inconsistency in routing, I'm not sure
> > how this happens but, it may be normal to get these from time to time when a
> > router is down and routes expires ...
> 
> There _are_ problems with Netatalk in that area (I can only get
> asun-2.1.[34] to work when I make the 1.4.1 machine a router) so a
> logged diagnostic had better made sense.

I'm not sure what your problem is but there are problems with netatalk routes
in 1.4.1, this was completely fixed post 1.4.2. Did you try a recent
-release branch ?

Anyway I'm not sure this message should be here in the first place.
Someone with more clues about netatalk internals should comment :)

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--