[ARMedslack] R: sysctl.conf not applied??

[Davide]

The firs thing that comes into my mins is that at the time rc.S loads your sysctl maybe not all the nfs modules have been bulled up.
Make sure rc.modules has all the modules you need for your nfs server and 
add "/sbin/sysctl -e -p /etc/sysctl.conf" somewhere just after running rc.modules but before starting nfs.

Regards
David

 

--- Lun 4/4/11, Robby Workman <rw at rlworkman.net> ha scritto:

> Da: Robby Workman <rw at rlworkman.net>
> Oggetto: [ARMedslack] sysctl.conf not applied??
> A: "Slackware ARM port" <armedslack at lists.armedslack.org>
> Data: Lunedì 4 Aprile 2011, 07:03
> I asked this on IRC a few moments
> ago, but I suspect there are 
> a few more sets of eyes here, soo...
> 
> Does anyone else try to set various params via
> /etc/sysctl.conf, 
> and if so, does it work correctly?  I set lockd (nfs)
> ports via 
> sysctl params, and on x86* hosts, that works as expected,
> but 
> not on arm hosts.  Here's my /etc/sysctl.conf
> contents: 
>   fs.nfs.nlm_udpport=4045
>   fs.nfs.nlm_tcpport=4045
> 
> It's supposed to run from rc.S, and I don't see why it
> wouldn't 
> be, but... on e.g. my NFS server, lockd gets random ports
> assigned.
> If I stop nfsd and run "/sbin/sysctl -e -p
> /etc/sysctl.conf" (which
> is exactly what rc.S does) and then restart rc.nfsd, lockd
> gets 
> assigned to port 4045 as desired.
> 
> Another set of eyes looking at that would be appreciated.
> 
> -RW
> _______________________________________________
> ARMedslack mailing list
> ARMedslack at lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>