Re: autofs reverts to IPv4 for multi-homed IPv6 server ?

[Ian Kent <raven@themaw.net>]

On Fri, 2016-04-08 at 16:29 +0200, Christof Koehler wrote:
> Hello,
> 
> apparently I confused my 5.1.1 source built experiment and my debian
> package rebuild experiment when I reported that libtirpc was used in
> my
> last email. So here is a new try to rebuild the deb source with
> --with-libtirpc.
> 
> I did a apt-get source autofs and added --with-libtirpc to debian
> rules.
> After that it would of course not allow me to build a package,
> "aborting
> due to unexpected upstream changes". So I just did a "dpkg
> -buildpackage
> -b" and then dpkg -i autofs... . Attached is the file build.out.gz
> which
> contains the stdout output. Clearly libtirpc is used somehow in the
> build.
> 
> After restoring maps in /etc I did a service restart autofs and with
> debug loglevel I get 
> 
> Apr  8 16:20:33 core324 automount[14615]: open_mount:247: parse(sun):
> cannot open mount module nfs
> (/usr/lib/x86_64-linux-gnu/autofs/mount_nfs.so: undefined symbol:
> clnt_dg_create)
> 
> as reported. I then double checked and actually
> 
> root@core324:~# ldd /usr/lib/x86_64-linux-gnu/autofs/mount_nfs.so
>         linux-vdso.so.1 =>  (0x00007ffff7ffd000)
>         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
> (0x00007ffff79f3000)
>         /lib64/ld-linux-x86-64.so.2 (0x0000555555554000)
> 
> no libtirpc. 

And yet the build from the log looks ok....
There's no even a link entry there which implies it hasn't been built
using libtirpc but the build looks like it is using it... puzzling.

Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in