netatalk is not running automatically after reboot


Subject: netatalk is not running automatically after reboot
From: Jolly Roger (jollyroger@nobox.com)
Date: Fri Jul 07 2000 - 01:42:14 EDT


I'm a relative Linux newbie, and was wondering if someone could help me set
it up so that netatalk runs automatically after a reboot. The installer did
not set that part up completely. What it is doing now, is a partial startup.
Immediately after booting up, if I do:

    ps uwax | grep atalkd

I get something like:

    root 3864 0.0 0.0 1184 88 ? S Jul05 0:00
/usr/local/atalk/etc/atalkd

However, I cannot access the computer from any macs on the network. :/

Just in case anyone is wondering...

    # find /etc/rc.d/ -name atalk

gives this:

    /etc/rc.d/init.d/atalk

Someone suggested I look at ntsysv, but it didn't list atalk, so I am lost
there.

if I examine
 at /var/log/messages, see:

Jul 4 17:25:20 microcosm atalk: starting appletalk daemons:
Jul 4 17:25:20 microcosm rc: Starting atalk succeeded
Jul 4 17:25:21 microcosm kernel: NET4: AppleTalk 0.18 for Linux NET4.0
Jul 4 17:25:21 microcosm atalkd[565]: restart (1.4b2+asun2.1.3)
Jul 4 17:25:21 microcosm sendmail: sendmail startup succeeded
Jul 4 17:25:22 microcosm atalkd[565]: zip_getnetinfo for eth0
Jul 4 17:25:22 microcosm gpm: gpm startup succeeded
Jul 4 17:25:24 microcosm httpd: httpd startup succeeded
Jul 4 17:25:26 microcosm xfs: xfs startup succeeded
Jul 4 17:25:26 microcosm xfs: Warning: The directory
"/usr/X11R6/lib/X11/fonts/100dpi" does not exist.
Jul 4 17:25:26 microcosm xfs: Entry deleted from font path.
Jul 4 17:25:26 microcosm linuxconf: Linuxconf final setup
Jul 4 17:25:28 microcosm rc: Starting linuxconf succeeded
Jul 4 17:25:31 microcosm atalkd[565]: zip_getnetinfo for eth0
Jul 4 17:25:41 microcosm atalkd[565]: zip_getnetinfo for eth0
Jul 4 17:25:51 microcosm atalkd[565]: config for no router
Jul 4 17:25:52 microcosm atalkd[565]: ready 0/0/0

Looks ok to me, so then why no access?

If I then do:
    
    /etc/rc.d/init.d/atalk stop

I get:

    # stopping appletalk daemons:[ OK ]
    [FAILED]

What the second FAILED means, I don't know. But if I then do:

    /etc/rc.d/init.d/atalk start

I get (after some moments):

    # starting appletalk daemons: atalkd nbprgstr papd afpd.

It takes a while (30 seconds or so). But after that, I can access the
computer from any mac on the network.

Something interesting: after all of this, if I do:

    /etc/rc.d/init.d/atalk stop

I get:

    # stopping appletalk daemons:[ OK ]
    [ OK ]

Aha...it didn't fail on the second thing.

I hope this provides some clue as to my problem. And I hope someone can
give me a clue as to why this is happening,

JR



This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:31:26 EST