Subject: Re: [netatalk-admins] netatalk not up on reboot
From: Vivek (vivek@imaginet.co.uk)
Date: Wed Jun 03 1998 - 05:54:07 EDT
On Tue, 2 Jun 1998, Danny Rice wrote:
[snip]
>>> it does. Typing /etc/rc.d/init.d/atalk.init start after reboot will
>>> also work. Any suggestions?
>> Are afpd/atalkd actually starting after the rc file has run its course?
> yes
>> Also, are these processes being started in the background?
> no
>> afpd can't be
>> started until atalkd has finished setting up: IIRC you have to run atalkd
>> in the foreground and wait for it to detach before starting afpd.
>>
>> What's actually in your '/etc/rc.d/init.d/atalk.init' ?
>
> it seems to work now on reboot. I added the 'sleep 5' before afpd is
> started. atalkd is started interactively and takes a long time, but I
> thought maybe afpd was started too soon after atalkd finished. Is it
> possible that this 'sleep 5' is making it work now?
> Here is what "atalk.init start" does. daemon is a sh function that
> starts jobs in the forground.
>
> case "$1" in
> start)
> echo -n "Starting AppleTalk services: "
> daemon atalkd
> nbprgstr -p 4 "${ATALK_NAME}:Workstation"
> nbprgstr -p 4 "${ATALK_NAME}:netatalk"
> daemon papd
> sleep 5
> daemon afpd ${AFPD_NOCLR} ${AFPD_NOAFS} ${AFPD_NOKRB} ${AFPD_NOGUEST} \
> -g ${AFPD_GUEST} -c ${AFPD_MAX_CLIENTS} -n ${ATALK_NAME}
> echo
> touch /var/lock/subsys/atalk
> ;;
I suppose the sleep 5 might be giving something enough time: what does
'daemon' do? Is it possible that 'daemon' shunts atalkd into the
background? This would explain why 'sleep 5' worked. [I'm guessing now;
Anyone care to shed any light?]
-- If voting could change things, it would be illegal.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:46 EST