Bugzilla Bug 172431

after installing nfs-utils 1.0.12-r2 with USE="tcpd -kerberos -nonfsv4" the nfs
startup failes because of missing /usr/sbin/rpc.gssd and /usr/sbin/rpc.svcgssd.
both files are required by the /etc/init.d/rpc.gssd init script which is being
installed with the specified use flags although the /usr/sbin/rpc.gssd
/usr/sbin/rpc.svcgssd files are only being installed when applying the kerberos
use flag.
so, whether the files are required for nfs server they should be installed or
if they are not required the init script shouldn't be installed.

Same problem here.

btw. the problem didn't change with nfs-utils-1.0.12-r3

and.. since it's a week without anything i wonder, is the problem being looked
into or just ignored?

how about you try some patience please

i'm sorry, i was too harsh..
i tried to look into it by myself since i don't really know what the gssd is
for i tried to make the gssd compile with it but it failed in configure looking
for libraries from kerberos dependencies so i assumed it should be without gssd
but then there is some dependency 'magic' in the startup scripts i didn't
really get so i stopped that journey because of very short time
basically it should be the same as the -r1 version but this one works, the new
one not... that's what i'm somewhat confused about...

fixed in cvs

hmm... i believe the idmapd is required for nfsv4 ?
but now the init script is not being installed with it...
...i had to configure the idmapd for the default user to be used in nfs4
...and somehow... the nfs and nfsmount scripts now look for the rpc.gssd init
script but it's not installed since gssd is not installed
i actually don't know what the gssd is needed for and why it is needed in my
config
i have several nfs entries and one nfs4 entry in my fstab and currently (on the
test system) only nfs v3 and no nfs4 service configured
(at the moment i use nfs4 without security)
if the gssd is needed for nfs4 without kerberos auth then it should still be
installed

i do believe you're correct ... ive swung it back so it's:
USE=kerberos -> controls rpc.gssd
USE=!nonfsv4 -> controls rpc.idmapd

ok, so far so good...
in my case nfs still hard-depends on rpc.gssd, i guess because of the nfs4
entry in /etc/fstab ?
the 'myneed=rpc.gssd' should only be there in case kerberos is installed, in
other cases it should only be 'mxuse=rpc.gssd', shouldn't it ?
i don't know if it would be better to use just need the rpc.gssd daemon or else
have different versions of the init script for the different settings of the
kerberos use flag
(i changed the script to use rpc.gssd and nfs seems to work)
btw: the nfsmount init script also 'need's the rpc.gssd, so this should be
changed too

i have yet to get nfsv4 to work, so i dont know what options would imply a
requirement on kerberos daemons

i have this one line in /etc/exports so and it works, it's without security at
all
(atm any access is done via one user 1000/100 (uid/gid))

# NFSv4 exports
/export.nfs4
emerald.home.localnet(rw,fsid=0,insecure,no_subtree_check,async,wdelay,all_squash,anonuid=1000,anongid=100

/etc/idmapd.conf the domain configured... 
it's working....

(very simple config)
i did some speed comparisons between nfs v3 and nfs4, i don't remember the
actual results but nfs4 was not just a little faster than nfs v3

this bug is actually the same as the newly opened bug #180428

=net-fs/nfs-utils-1.1.0

/etc/init.d/nfsmount

 -- requires /etc/init.d/rpc.gssd to start even though nfs-utils was compiled
with -kerberos, else it fails every time.


To resolve for now, I commented out "myneed" & "myuse" for rpc.gssd.  Figure
since things are moving rapidly away from rpc.gssd/kerberos to SPKM-3/LIPKEY
(also noticing dereferencing errors within libgss compile).  Unless using
Kerberos will resolve my chown problems on NFS4 exports (as they're mapped to
nobody:nobody), I'm not going to mess with kerberos for now.

BTW: Even if I compiled with the use flag "kerberos", =net-fs/nfs-utils-1.1.0
/etc/init.d/nfsmount will fail to start due to a rpc.gssd error.  But simply
commenting out or just doing mount -a -t nfs4 will succeed as I'm apparently
not configured to even use Kerberos!

the nfs initd script no longer needs idmapd ... it will need gssd only if
exportfs contains a sec= line

the nfsmount initd script checks /etc/fstab and will need idmapd for any nfs4
mount and gssd for any mount that has sec=