Strange atalk behaviour
Hi, folks! again a strange behavoiur here which I cant hendle alone ;-) netatalk on a Suse 8.1 w/ 2.4.19 and netatalk 1.5.3.1-71 was running for about 3 - 4 weeks without problems. users have their folders, shadowed passwords, can log in and so on. since yesterday - and I swear I changed NOTHING on any configurationfile!! - when the user logs in, no volumes are visible... rcatalk status says: papd: OK afpd: OK timelord: No process atalkd: No process /var/log/messages says: setifaddr: eth0 - invalid argument. try specifying a smaller net range. BUT NOW (!) it´s getting even better and more funny: we have another machine in the same subnet with identical config (suse, kernel, atalk), where the user can see and use their volumes - and rcatalk status and /var/log/messages saying exactly the same things!!! We have a NT box which is doing the seed routing here... it may be a problem with that box. when I close down the NT machine, rcatalk status says: papd: No process afpd: No process timelord: No process atalkd:OK 1. Do anyone have had similar experiences? 2. why (why, why, why...) did it work for some weeks (i didnt reboot the atalk-linux-box in that time) and suddenly shows the strange behaviour with no volumes visible (though accepting the user with his password)? thanx in advance for hints et.al. lars -- http://www.ruebenschweine.de Try also: http://www.warzenpower.de +++ http://www.lars-und-sandra.de +++ http://www.r100rt.de Diese email wurde automatisch generiert, Sie können deshalb nicht darauf antworten; webmaster@warzenpower.de
participants (1)
-
lars