t happens because my kernels don't have any of the modules
from the hidden_dep_add_modules() function. I'll leave it up to you
to decide if its better to never call manual_add_modules without
arguments, or make manual_add_modules a nop if it is.
--
Jamie Heilman http:
es since 0.100 that introduced this message).
--
Jamie Heilman http://audible.transient.net/~jamie/
"Paranoia is a disease unto itself, and may I add, the person standing
next to you may not be who they appear to be, so take precaution."
is essentially a misconfiguration. Domain should be set to your
NFSv4 Domain Name. See RFC3530 section 5.8, or RFC5661 section 5.9.
Multi-domain NFSv4 is still in draft:
http://tools.ietf.org/html/draft-adamson-nfsv4-multi-domain-access-04
--
Jamie Heilman http://audible.tra
Anders Boström wrote:
> >>>>> "SW" == Stephan Windmüller writes:
>
> SW> On 23.10.2011 13:49, Jamie Heilman wrote:
> >> Chances are you all have your nfsidmap Domain mismatched between
> >> client and server; check your user.* sysl
Stephan Windmüller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 24.10.2011 00:58, Jamie Heilman wrote:
>
> >> In my configuration both domains (client and server) are
> >> correctly set, but this is not the issue: passwd and group data
&g
Stephan Windmüller wrote:
> On 23.10.2011 13:49, Jamie Heilman wrote:
>
> > Chances are you all have your nfsidmap Domain mismatched between
> > client and server; check your user.* syslog logs on the client for
> > messages like: nfsidmap: nss_getpwnam: name 'f
onf on
the server, unless your fqdn happens to be funky, in which case you
should just set Domain explicitly.
--
Jamie Heilman http://audible.transient.net/~jamie/
"You came all this way, without saying squat, and now you're trying
to tell me a '56 Chevy can bea
7 matches
Mail list logo
