Package: nfs-common
Version: 1:1.2.6-3
Followup-For: Bug #657497
I have just come across the same issue, but in my case the `exec` option
is being ignored when used in conjunction with the `users` option,
even when `exec` coming after `users`.
With `/etc/fstab` containing
labrador:/oneforall /oneforall nfs auto,exec 0 0
the `exec` option is obeyed:
labrador:/oneforall on /oneforall type nfs
(rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.2,mountvers=3,mountport=57298,mountproto=udp,local_lock=none,addr=192.168.0.2)
However, with `/etc/fstab` containing
labrador:/oneforall /oneforall nfs users,auto,exec 0 0
the `exec` option is _not_ obeyed:
labrador:/oneforall on /oneforall type nfs
(rw,nosuid,nodev,noexec,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.2,mountvers=3,mountport=57298,mountproto=udp,local_lock=none,addr=192.168.0.2)
This is a regression, and should be fixed.
-- Package-specific info:
-- rpcinfo --
program vers proto port
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 44901 status
100024 1 tcp 53640 status
100021 1 udp 35126 nlockmgr
100021 3 udp 35126 nlockmgr
100021 4 udp 35126 nlockmgr
100021 1 tcp 37294 nlockmgr
100021 3 tcp 37294 nlockmgr
100021 4 tcp 37294 nlockmgr
-- /etc/default/nfs-common --
NEED_STATD=
STATDOPTS=
NEED_IDMAPD=
NEED_GSSD=
-- /etc/idmapd.conf --
[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
[Mapping]
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
labrador:/oneforall /oneforall nfs auto,exec 0 0
-- /proc/mounts --
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
labrador:/oneforall /oneforall nfs
rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.2,mountvers=3,mountport=57298,mountproto=udp,local_lock=none,addr=192.168.0.2
0 0
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nfs-common depends on:
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-35
ii libc6 2.13-38
ii libcap2 1:2.22-1.2
ii libcomerr2 1.42.5-1
ii libdevmapper1.02.1 2:1.02.74-6
ii libevent-2.0-5 2.0.19-stable-3
ii libgssglue1 0.4-2
ii libk5crypto3 1.10.1+dfsg-3
ii libkeyutils1 1.5.5-4
ii libkrb5-3 1.10.1+dfsg-3
ii libmount1 2.20.1-5.3
ii libnfsidmap2 0.25-4
ii libtirpc1 0.2.2-5
ii libwrap0 7.6.q-24
ii lsb-base 4.1+Debian9
ii rpcbind 0.2.0-8
ii ucf 3.0025+nmu3
Versions of packages nfs-common recommends:
ii python 2.7.3-3
Versions of packages nfs-common suggests:
pn open-iscsi <none>
pn watchdog <none>
Versions of packages nfs-kernel-server depends on:
ii libblkid1 2.20.1-5.3
ii libc6 2.13-38
ii libtirpc1 0.2.2-5
ii libwrap0 7.6.q-24
ii lsb-base 4.1+Debian9
ii ucf 3.0025+nmu3
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
