On Fri, 1 Apr 2011, Rick Macklem wrote:
Since rpc.lockd and rpc.statd expect to be able to do IP broadcast
(same goes for rpcbind), I suspect that might be a problem w.r.t.
jails, although I know nothing about how jails work?
Oh, and you can use the nolock mount option to avoid use of
On Fri, 1 Apr 2011, Rick Macklem wrote:
Since rpc.lockd and rpc.statd expect to be able to do IP broadcast
(same goes for rpcbind), I suspect that might be a problem w.r.t.
jails, although I know nothing about how jails work?
Oh, and you can use the nolock mount option to avoid use of
I just setup an nfs mount between two servers ...
ServerA, nfsd on 192.168.1.8
ServerB, nfs client on 192.168.1.7
I have a jail, ServerC, running on 192.168.1.7 ... most operations appear
to work, but it looks like 'special files' of a sort aren't working, for
when I try and startup Apache,
I've succeedig in getting a bit further ... by the time I got to the
bottom of my original, I started to think in terms of rpc more, and had
overlooked lookign at thte rpcbind man page, which *does* have a -h option
... setting that fixes things perfectly *almost* ...
The last issue I seem
I just setup an nfs mount between two servers ...
ServerA, nfsd on 192.168.1.8
ServerB, nfs client on 192.168.1.7
I have a jail, ServerC, running on 192.168.1.7 ... most operations
appear
to work, but it looks like 'special files' of a sort aren't working,
for
when I try and startup
I just setup an nfs mount between two servers ...
ServerA, nfsd on 192.168.1.8
ServerB, nfs client on 192.168.1.7
I have a jail, ServerC, running on 192.168.1.7 ... most operations
appear
to work, but it looks like 'special files' of a sort aren't working,
for
when I try and
