Control: reassign -1 rpcbind
This bug has been reported against rpcinfo which is no longer shipped in
libc-bin, but rather in rpcbind. I could not tell off-hand if it still
relevant.
Cheers,
Sven
Am 25.06.2010 um 21:46 schrieb Alexander Kretschmer:
> Package: libc-bin
> Version: 2.10.2-6
> Severity: important
>
>
>
> -- System Information:
> Debian Release: 5.0.4
> APT prefers stable
> APT policy: (990, 'stable')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.27.10 (SMP w/2 CPU cores)
> Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
> Shell: /bin/sh linked to /bin/bash
>
> When runnig nfs 3 on TCP and UDP rpcinfo shows the following
>
> rpcinfo -p
> Program Vers Proto Port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 100024 1 udp 33934 status
> 100024 1 tcp 40718 status
> 100021 1 udp 54228 nlockmgr
> 100021 3 udp 54228 nlockmgr
> 100021 4 udp 54228 nlockmgr
> 100021 1 tcp 57003 nlockmgr
> 100021 3 tcp 57003 nlockmgr
> 100021 4 tcp 57003 nlockmgr
> 100003 3 udp 2049 nfs
> 100003 3 tcp 2049 nfs
> 100005 1 udp 41087 mountd
> 100005 1 tcp 44256 mountd
> 100005 2 udp 41087 mountd
> 100005 2 tcp 44256 mountd
> 100005 3 udp 41087 mountd
> 100005 3 tcp 44256 mountd
>
> When running nfs on TCP only it shows this:
>
> rpcinfo -p
> Program Vers Proto Port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 100024 1 udp 33934 status
> 100024 1 tcp 40718 status
> 100021 1 udp 38327 nlockmgr
> 100021 3 udp 38327 nlockmgr
> 100021 4 udp 38327 nlockmgr
> 100021 1 tcp 45910 nlockmgr
> 100021 3 tcp 45910 nlockmgr
> 100021 4 tcp 45910 nlockmgr
> 100003 3 tcp 2049 nfs
> 100005 1 udp 50650 mountd
> 100005 1 tcp 41600 mountd
> 100005 2 udp 50650 mountd
> 100005 2 tcp 41600 mountd
>
> You can see that mountd isnt running in Vers 3. The init.d script for
> nfs-kernel-server checks weather nfs is running in vers 3 by calling
>
> rpcinfo -u localhost nfs 3
>
> It gets as an answer that program 100003 isn't registered. Its working fine
> if nfs is running on udp or both udp and tcp.
