Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #56226 > unrolled thread

Bug#848277: nfs-common: /usr/sbin/start-statd: 10: exec: 200: not found

Back to article view | Back to linux.debian.kernel

Contents

  Bug#848277: nfs-common: /usr/sbin/start-statd: 10: exec: 200: not found Sven Joachim <svenjoac@gmx.de> - 2016-12-15 22:50 +0100
    Bug#848277: marked as done (nfs-common: /usr/sbin/start-statd:  10: exec: 200: not found) owner@bugs.debian.org (Debian Bug Tracking System) - 2016-12-17 12:30 +0100

#56226 — Bug#848277: nfs-common: /usr/sbin/start-statd: 10: exec: 200: not found

Package: nfs-common
Version: 1:1.3.4-1
Severity: important

Even after fixing nfs-config.service (see #848145), I could no longer
use my NFS 3 mounts because rpc.statd failed to start:

,----
| /usr/sbin/start-statd: 10: exec: 200: not found
`----

That's because dash, unlike bash, does not support file descriptors
higher than 9 in redirection and treats the command as if it had been
"exec 200 > /var/run/rpc.statd.lock".

According to POSIX.1-2008[1], you cannot rely on a number higher than 9
here:

,----
| The largest possible value is implementation-defined; however, all
| implementations shall support at least 0 to 9, inclusive, for use by the
| application.
`----

Indeed, using 9 rather than 200 actually works.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-pavil+ (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-common depends on:
ii  adduser              3.115
ii  init-system-helpers  1.46
ii  keyutils             1.5.9-9
ii  libc6                2.24-8
ii  libcap2              1:2.25-1
ii  libcomerr2           1.43.3-1
ii  libdevmapper1.02.1   2:1.02.136-1
ii  libevent-2.0-5       2.0.21-stable-2.1
ii  libgssapi-krb5-2     1.15-1
ii  libk5crypto3         1.15-1
ii  libkeyutils1         1.5.9-9
ii  libkrb5-3            1.15-1
ii  libmount1            2.29-1
ii  libnfsidmap2         0.25-5
ii  libtirpc1            0.2.5-1
ii  libwrap0             7.6.q-25
ii  lsb-base             9.20161125
ii  rpcbind              0.2.3-0.5
ii  ucf                  3.0036

Versions of packages nfs-common recommends:
ii  python  2.7.11-2

Versions of packages nfs-common suggests:
pn  open-iscsi  <none>
pn  watchdog    <none>

-- no debconf information


1. http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html (§2.7)

[toc] | [next] | [standalone]

#56259 — Bug#848277: marked as done (nfs-common: /usr/sbin/start-statd: 10: exec: 200: not found)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sat, 17 Dec 2016 11:18:56 +0000
with message-id <E1cID0y-000FOR-0v@fasolo.debian.org>
and subject line Bug#848277: fixed in nfs-utils 1:1.3.4-2
has caused the Debian Bug report #848277,
regarding nfs-common: /usr/sbin/start-statd: 10: exec: 200: not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
848277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848277
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web