Subject: Re: starting appletalk daemons: socket: Invalid argument
From: Moritz Kaiser (ariser@fs.tum.de)
Date: Sun May 07 2000 - 10:11:28 EDT
On Sun, 7 May 2000, David Blache wrote:
> on 5/6/2000 5:05 PM, Moritz Kaiser at ariser@fs.tum.de wrote:
>
> > Hi,
> >
> > the first thing to do is to check, whether your NIC is working. Try ping,
> > or analyze your /var/log/messages regarding your NIC.
> > On my machine this looks like this:
> > 8<-------------------*snip*
> > May 5 23:48:47 x kernel: 3c515.c:v0.99 4/7/98 becker@cesdis.gsfc.nasa.gov
> > May 5 23:48:47 x kernel: 3c515 Resource configuration register 0x008f,
> > DCR0483.
> > May 5 23:48:47 x kernel: eth0: 3c515 at 0x280, 00:10:4b:9c:7e:ef, DMA3,
> > IRQ 15
> > May 5 23:48:47 x kernel: 64k word-wide RAM 1:1 Rx:Tx split,
> > autoselect/10baseT interface.
> > May 5 23:48:47 x kernel: 1 3c515 cards found.
> > 8<-------------------*snip*
>
> I'm not using NIC (mainly because I don't know enough about it, or how to
> configure it). If anyone would like to give a brief explanation of what it
> is, and whether or not I should be running it, I'd be appreciative.
NIC=Network Interface Card. Your (probably) Ethernet Adapter. Any module
oder kernel driver has to be run for you to be able to connect to any LAN.
If your kernel doesn't support any NIC's you have to build a new one.
*grin*
In "make menuconfig" you'll find NIC-support at "Network device support".
But in most cases your kernel already is supporting certain standard
NICs. But check this out anyway.
>
> > Then ensure your kernel has appletalk support enabled. Otherwise build a
> > new kernel including appletalk support.
>
> It wasn't enabled. I've enabled it.
>
> 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. :/
Are the netatalk daemons running after beeing started manually? Watch for
it by typing "ps aux | grep afpd" and "ps aux | grep papd" and
"ps aux | grep atalkd".
If not, there might be a general problem with networking, as mentioned
above.
Greetings,
Moritz
__________________________________________________________
Moritz Kaiser
Studentische Vertretung, Technische Universitaet Muenchen
Europe / Germany
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:38 EST