Subject: RE: [netatalk-admins] Confiuration
From: Benjamin Lee (ben@power-net.com.au)
Date: Tue Aug 31 1999 - 21:47:12 EDT
__________________________________________________________________
What does not destroy me, makes me stronger.
-- Nietzsche
On Tue, 31 Aug 1999, Tom Tilmant wrote:
> It was Red Hat 6.0. Which RPM were you using?
> netatalk-1.4b2+asun2.1.0-5.rpm or netatalk-1.4b2+asun2.1.3-6.rpm.
>
> Tom Tilmant
i am using netatalk-1.4b2+asun2.1.3-6.rpm.
what i just found is that it does work.... BUT only ONCE.
if i turn off atalkd in ntsysv then
if i manually run:
/etc/rc.d/init.d/atalk start
it seems to work fine...
however AS SOON as i do a /etc/rc.d/init.d/atalk restart
i get things like this...
Sep 1 11:41:02 chaos atalkd[1578]: restart (1.4b2+asun2.1.3)
Sep 1 11:41:13 chaos atalkd[1578]: ready 0/0/0
Sep 1 11:41:13 chaos atalk: atalkd startup succeeded
Sep 1 11:41:13 chaos atalkd[1578]: setifaddr: eth0: Address already in
use
Sep 1 11:41:13 chaos atalk: papd startup succeeded
Sep 1 11:41:13 chaos papd[1591]: restart (1.4b2+asun2.1.3)
Sep 1 11:41:14 chaos papd[1591]: atp_open: Cannot assign requested
address
and on the console
bind: Cannot assign requested address
bind: Cannot assign requested address
my setup is simple...
my linux box has two network cards (RJ45) each card is connected via
direct crossover cable to a single mac.
as i mentioned earlier it's worked fine for me in 5.2
i think it has something to do with how the 'stop' is defined in
init.d/atalk
what do you think?
ben
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:17:10 EST