[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

singular nfs mounting problem



i have two hosts on a different subnet from our NFS server. DNS
resolution and normal IP traffic is flawless.

The NFS server has a custom 2.4.19 kernel with grsecurity 1.9.6, but
none of grsecurity's features are enabled (sysctl is enabled and
nothing in /proc has been touched). It exports the following:

  /export time(rw,all_squash,anongid=503)
  /export cigar(rw,all_squash,anongid=503)
  /export sky(rw,all_squash,anongid=503)

(is there a way to set default arguments, so that i don't have to
specify them in every line over and over again.

time, cigar, and sky all have the following in /etc/fstab:

  piper:/export /piper nfs defaults,hard,noauto,user 0 0

time can happily mount /piper. piper's syslog notes this as follows:

  rpc.mountd: authenticated mount request from
  time.home.madduck.net:762 for /export (/export) 

but when i try to mount /piper on cigar or sky, mount will just hang
there forever. to this, piper's syslog says:

  rpc.mountd: authenticated mount request from
  cigar.home.madduck.net:944 for /export (/export) 

  kernel: grsec: CAP_FSETID not raised for (nfsd:16764) UID(0)
  EUID(0), parent (init:1) UID(0) EUID(0)

What gives? How should I go about and solve this?

Thanks!

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck
 
"the well-bred contradict other people.
 the wise contradict themselves."
                                                        -- oscar wilde

Attachment: pgpgkDzfqoUGE.pgp
Description: PGP signature


Reply to: