Package: nfs-common
Version: 1:1.0.9-5
Severity: normal

Starting nfs-common gives the following:

Starting NFS common utilities: statd idmapd gssdcan't open 
/usr/lib/libgssapi_krb5.so: /usr/lib/libgssapi_krb5.so: cannot open shared 
object file: No such file or directory
rpc.gssd: Problem with gssapi library

I have the following files:

~$ ls -l /usr/lib/libgssapi_krb5.so*
lrwxrwxrwx 1 root root     21 2006-07-28 11:12 /usr/lib/libgssapi_krb5.so.2 -> 
libgssapi_krb5.so.2.2
-rw-r--r-- 1 root root 111676 2006-07-16 18:43 /usr/lib/libgssapi_krb5.so.2.2

Perhaps my symlinks are wrong? (I didn't touch them manually.)

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc1-wl
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)

Versions of packages nfs-common depends on:
ii  adduser                      3.95        Add and remove users and groups
ii  libc6                        2.3.6-15    GNU C Library: Shared libraries
ii  libcomerr2                   1.39-1      common error description library
ii  libevent1                    1.1a-1      An asynchronous event notification
ii  libgssapi2                   0.10-2      A mechanism-switch gssapi library
ii  libkrb53                     1.4.3-8     MIT Kerberos runtime libraries
ii  libnfsidmap1                 0.16-3      An nfs idmapping library
ii  librpcsecgss2                0.13-2      allows secure rpc communication us
ii  lsb-base                     3.1-10      Linux Standard Base 3.1 init scrip
ii  portmap                      5-20        The RPC portmapper
ii  sysvinit                     2.86.ds1-15 System-V-like init utilities
ii  ucf                          2.0012      Update Configuration File: preserv

nfs-common recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to