Subject: Re: [netatalk-admins] Restarting daemons on Linux
From: Brian Bergstrand (bbergstrand@niu.edu)
Date: Fri Feb 20 1998 - 17:12:29 EST
>Jonathan Peterson <jon@amxdigital.com> tastet:
>> I looked into this a while ago and I got the impression that it was a well
>> known problem with no solution.
>>
>> Bascially, If I stop all the various netatalk daemons (with killall, or
>> kill), and then try and start them again, I get the error:
>> Appletalk not up! Child exited with 1
>...
>
>I have found that with this stop section in my SysV style atalk rc script:
>
[snip rc]
>and running the stop procedure *twice* appletalk will be dead afterwards
>and can be restarted. It is only works when appletalk is a module.
>
>Nicolai
There seems to be this consensus that having atalk in the kernel is a bad
thing, not true. If people would update to the latest kernel 2.0.33 (or
.32), recompile with the new kernel headers, they can stop and start atalk
to their hearts content. On my machine, the atalk daemon started with a pid
of around 80, it now has one in the 18,000's and is running fine. (I have
quit and restarted the server at least 5 times with never an error.)
Config:
Slak 3.4, kernel 2.0.33 w/atalk in kernel
32MB RAM
netatalk 1.4b2+asun18.2
Brian
Brian Bergstrand
Network Specialist - ACS
Northern Illinois University
815-753-8547
bbergstrand@niu.edu
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:31:06 EST