Re: starting appletalk daemons: socket: Invalid argument


Subject: Re: starting appletalk daemons: socket: Invalid argument
From: Bob Rogers (rogers-netatalk@rgrjr.dyndns.org)
Date: Mon May 08 2000 - 16:48:03 EDT


   From: David Blache <alterego@austin.rr.com>
   Date: Sun, 07 May 2000 15:43:33 -0500

   on 5/7/2000 2:53 PM, Bob Rogers at rogers-netatalk@rgrjr.dyndns.org wrote:

> From: David Blache <alterego@austin.rr.com>
> Date: Sun, 07 May 2000 02:05:51 -0500
>>
>>> on 5/6/2000 5:05 PM, Moritz Kaiser at ariser@fs.tum.de wrote:
>>>
>>> . . .
>>
>> But when I reboot the machine atalk starts up, but afpd and company do NOT
>> start up. Can someone give me a clue as to why not? The atalk.init script
>> is in /etc/rc.d/init.d/atalk.init. Seems like that should be enough to get
>> afpd and friends going. But I always have to run the script manually to get
>> them going after a restart. :/
>
> Here's my $0.02 for due diligence: Have you made the appropriate links
> from the /etc/rc.d/rc*.d/ directories?

   I wasn't aware that I was supposed to have anything anywhere but in
   /etc/rc.d/init.d/ Why would I make links to the other directories?

Not to; from those directories. There is one directory for each run
level; each such directory has "K??service" symbolics links to
../init.d/service to bring "service" down, and "S??service" links to
start "service" up. The numbers are used to control the order in which
services are brought up or down, and do not have to be unique.

   Here's what my atalk setup looks like. I normally operate at run
level 3. atalkd is started at levels 3 through 5; I think I picked
these to correspond to NFS.

    rgr> find /etc/rc.d -name '*atalk' -ls
    278714 2 -rwxr--r-- 1 root root 1878 Aug 3 1999 /etc/rc.d/init.d/atalk
    280970 1 lrwxrwxrwx 1 root root 15 Jan 25 19:53 /etc/rc.d/rc0.d/K35atalk -> ../init.d/atalk
    305300 1 lrwxrwxrwx 1 root root 15 Jan 25 19:53 /etc/rc.d/rc1.d/K35atalk -> ../init.d/atalk
    311435 1 lrwxrwxrwx 1 root root 15 Jan 25 19:53 /etc/rc.d/rc2.d/K35atalk -> ../init.d/atalk
    315625 1 lrwxrwxrwx 1 root root 15 Jan 25 19:53 /etc/rc.d/rc3.d/S91atalk -> ../init.d/atalk
    323895 1 lrwxrwxrwx 1 root root 15 Jan 25 19:53 /etc/rc.d/rc4.d/S91atalk -> ../init.d/atalk
    327978 1 lrwxrwxrwx 1 root root 15 Jan 25 19:53 /etc/rc.d/rc5.d/S91atalk -> ../init.d/atalk
    331945 1 lrwxrwxrwx 1 root root 15 Jan 25 19:53 /etc/rc.d/rc6.d/K35atalk -> ../init.d/atalk
    rgr>

To create these, I did something like

        # cd /etc/rc.d
        # for dir in rc3.d rc4.d rc5.d; do
> ln -s ../init.d/atalk $dir/S91atalk
> done
        #

and similarly for the "K35atalk" links. I'm running Red Hat 6.0, so
this exact recipe will (probably) work to your machine. "man init" and
the SAG (System Administrators' Guide) can tell you more about the
startup sequence.

   Please forgive my ignorance. I've only been with Linux for a few months.

No problem; I've been there myself (quite recently, too).

                                        -- Bob Rogers



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