On Sun, Dec 29, 2013 at 7:36 PM, Ian Kent <raven@xxxxxxxxxx> wrote:
> On Fri, 2013-12-27 at 15:30 +0800, Dennis Lan (dlan) wrote:
>> sorry, I was not accurate about the failure cases.
>>
>> using commit ec267c2c406256e401540e5bc890b2e0c2ff6c35
>>
>> snip from file /etc/autofs/auto.misc
>> mkynfs -ro,soft,intr,nfsvers=3 192.168.90.12:/home/dennis
>> mkydns -ro,soft,intr,nfsvers=4 mickeycn:/home/dennis
>>
>> with libtirpc enabled (all other features disabled),[1]
>> "ls /mnt/misc/mkynfs" lead to automount segfault
>> "ls /mnt/misc/mkydns" automount fail (no crash), but report "no hosts available"
>>
>> with libtirpc disabled (all other features disabled)[2]
>> "ls /mnt/misc/mkynfs" automount fail (no crash), report "no hosts available"
>> "ls /mnt/misc/mkydns" works fine
>
> What exactly does "all other features disabled" mean from a configure
> POV. I always use --disable-mount-locking and --enable-ignore-busy,
> always.
>
$ /var/tmp/portage/net-fs/autofs-9999/work/autofs-9999/configure
--prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
--sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64
--docdir=/usr/share/doc/autofs-9999 --with-confdir=/etc/conf.d
--with-mapdir=/etc/autofs --with-dmalloc --with-openldap
--with-libtirpc --with-sasl --with-hesiod --disable-mount-locking
--disable-ext-env --enable-sloppy-mount --enable-force-shutdown
--enable-ignore-busy --with-systemd=/usr/lib/systemd/system
RANLIB=/usr/bin/x86_64-pc-linux-gnu-ranlib
# automount --version
Linux automount version 5.0.8
Directories:
config dir: /etc/conf.d
maps dir: /etc/autofs
modules dir: /usr/lib64/autofs
Compile options:
DISABLE_MOUNT_LOCKING ENABLE_FORCED_SHUTDOWN ENABLE_IGNORE_BUSY_MOUNTS
WITH_HESIOD WITH_LDAP WITH_SASL WITH_DMALLOC LIBXML2_WORKAROUND
WITH_LIBTIRPC
> Maybe that's something to do with the problem your seeing .....
>
> Ian
>
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
