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

Bug#633426: nfs-kernel-server: complains about missing /etc/exports.d directory



Package: nfs-kernel-server
Version: 1:1.2.4-1
Severity: minor

I just saw the following warning:

,----
| # /etc/init.d/nfs-kernel-server start
| Exporting directories for NFS kernel daemon...exportfs: scandir /etc/exports.d: No such file or directory
| 
| .
| Starting NFS kernel daemon: nfsd mountd.
`----

Creating the missing directory made nfs-kernel-server shut up, so maybe
it should just be shipped in the package.


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

Kernel: Linux 3.0.0-rc6-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nfs-kernel-server depends on:
ii  libblkid1          2.19.1-2              block device id library
ii  libc6              2.13-10               Embedded GNU C Library: Shared lib
ii  libcomerr2         1.42~WIP-2011-07-02-1 common error description library
ii  libgssapi-krb5-2   1.9.1+dfsg-1          MIT Kerberos runtime libraries - k
ii  libgssglue1        0.3-1                 mechanism-switch gssapi library
ii  libk5crypto3       1.9.1+dfsg-1          MIT Kerberos runtime libraries - C
ii  libkrb5-3          1.9.1+dfsg-1          MIT Kerberos runtime libraries
ii  libnfsidmap2       0.24-1                An nfs idmapping library
ii  libtirpc1          0.2.2-4               transport-independent RPC library
ii  libwrap0           7.6.q-21              Wietse Venema's TCP wrappers libra
ii  lsb-base           3.2-27                Linux Standard Base 3.2 init scrip
ii  nfs-common         1:1.2.4-1             NFS support files common to client
ii  ucf                3.0025+nmu2           Update Configuration File: preserv

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information



Reply to: