summaryrefslogtreecommitdiff
path: root/kernel/intermodule.c
diff options
context:
space:
mode:
authorAndrew Morton <akpm@osdl.org>2004-05-24 18:36:31 -0700
committerLinus Torvalds <torvalds@ppc970.osdl.org>2004-05-24 18:36:31 -0700
commited8d9961f3c411b5b3ab2a673e66bfc01827a46b (patch)
tree940d98a46fc1d9524d3d8a7ac40d4175420fd2a3 /kernel/intermodule.c
parent7190b86d8c48217c158dae34dff754a953381197 (diff)
[PATCH] Prevent scary warnings from knfsd
From: "J. Bruce Fields" <bfields@fieldses.org> The kernel currently prints: nfsd: nobody listening for auth.unix.ip upcall; has some daemon not been started? on every bootup, during initscripts. Neil Brown <neilb@cse.unsw.edu.au> says: It was part of the recent set of idmapper patches. Bruce wanted the admin to get a warning when the idmapper daemon wasn't running. I thought the same warning should apply to any daemon that responded to upcalls. In the case of auth.unix.ip it isn't strictly necessary for a daemon to be running (for comparability with 2.4). You can get rid of the warning by doing: mount -t nfsd nfsd /proc/fs/nfs before mountd is started (init scripts should start doing this I hope, but distributions don't tend to use the init script from nfs-utils, so it is hard to push it). This will trigger mountd to listen on auth.unix.ip and others. That's a hassle, so Bruce's patch limits the warning purely to the new idmapper cache. It provides a callback in the cache_detail that individual caches can use to log messages when upcalls fail because a userspace daemon not running. Implement this method for the idmapping caches.
Diffstat (limited to 'kernel/intermodule.c')
0 files changed, 0 insertions, 0 deletions