[OpenAFS-devel] Accomodating daemons

[Erik Osterman]

I disabled openafs-client from autostarting at boot.
To /etc/openvpn/openvpn.conf, I added

route-up "/etc/init.d/openafs-client start"
down-pre "/etc/init.d/openafs-client stop"

df shows...

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1              8064432   2343764   5311020  31% /
/dev/sda2            153915428    192672 145904312   1% /mnt
AFS                    9000000         0   9000000   0% /afs

It mounted alright..

fs getclientaddrs
1.2.3.4
10.0.0.6

It lists both the public and private IPs.

# ls /afs/ourdomain.com/
ls: /afs/ourdomain.com/: Permission denied


Back to the drawing board...


Erik Osterman





Derrick J Brashear wrote:
> On Sun, 26 Nov 2006, Erik Osterman wrote:
>
>> It would appear that openvpn is started before openafs-client. In 
>> addition, I've restarted the openafs-client several times after 
>> reboot with no avail.
>>
>> openvpn         0:off   1:off   2:off   3:off   4:on    5:off   6:off
>> openafs-client  0:off   1:off   2:on    3:on    4:on    5:on    6:off
>>
>> rc.d/rc4.d/S24openvpn
>> rc.d/rc4.d/S50openafs-client
>>
>>
>> Though after a reboot, I realize "fs getclientaddrs" no longer lists 
>> our internal 10 ip, but just our public IP.
>>
>>
>> Should I have OpenVPN call "/etc/init.d/openafs-client start" when 
>> the link comes up, instead of relying on the rc.d init order?
>
> You could try, I'd be interested to know if that helps anything.
>
> Derrick
>
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel