[blfs-support] Autofs problem on LFS7.2
lfs65 at cruziero.com
Wed Mar 27 14:50:23 PDT 2013
> Date: Wed, 27 Mar 2013 17:24:34 -0400
> From: "Cliff McDiarmid" <cliffhanger at gardener.com>
> To: "akhiezer" <lfs65 at cruziero.com>,
> "BLFS Support List"
> <blfs-support at linuxfromscratch.org>
> Subject: Re: [blfs-support] Autofs problem on LFS7.2
> > With automount not running, remove the empty dir (iff it's empty) /testautomount ,
> > and retry the 'automount -v -f -d /etc/auto.master', see if it the
> > whole path '/testautomount/sandisk', shows the contents of the usbstick ok under
> > '/testautomount/sandisk', and then when you exit automount, does it remove the
> > entire path '/testautomount/sandisk' ?
> Ok. It auto-generates '/testautomount' when started with 'automount -v -f -d /etc/auto.master', but not '/testautomount/sandisk'.
> Only the following again is shown under '/testautomount':
> total 4
> drwxr-xr-x 2 root root 0 Mar 27 21:01 ./
> drwxr-xr-x 26 root root 4096 Mar 27 21:01 ../
> When I exit automount the '/testautomount' disappears. In the meantime the following diagnostics appear untill I stop autofs:
> handle_packet: type = 3
> handle_packet_missing_indirect: token 1, name sandisk, request pid 1996
> attempting to mount entry /testautomount/sandisk
> lookup_mount: lookup(program): looking up sandisk
> lookup(program): lookup for sandisk failed
> dev_ioctl_send_fail: token = 1
- the (zeroeth and) first thing that the appearances of 'token' in the above,
and the general structure and tone of the messages, shouts to me, is 'kerberos'.
Cliff, I know the proverbial 'less than epsilon', about kerberos, in practice
I think this would need some input from someone who knows kerberos well - IIRC Randy?
Will have an at least token (sic) look at the kerberos page to see if there's a
simple config entry or so needed - but I kinda doubt it: and more importantly I
don't want to be wasting your time with low-knowledge 'advice'.
Will also have a look at the autofs 5.0.7 build cfg to see if kerberos can be
switched off easily - or do you need it for other stuff?
> failed to mount /testautomount/sandisk
> st_expire: state 1 path /testautomount
> expire_proc: exp_proc = 3060792128 path /testautomount
> expire_cleanup: got thid 3060792128 path /testautomount stat 0
> expire_cleanup: sigchld: exp 3060792128 finished, switching from 2 to 1
> st_ready: st_ready(): state = 2 path /testautomount
> ^Cdo_notify_state: signal 2
> master_notify_state_change: sig 2 switching /testautomount from 1 to 5
> st_prepare_shutdown: state 1 path /testautomount
> expire_proc: exp_proc = 3059739456 path /testautomount
> expire_cleanup: got thid 3059739456 path /testautomount stat 0
> expire_cleanup: sigchld: exp 3059739456 finished, switching from 5 to 7
> st_shutdown: state 5 path /testautomount
> umount_multi: path /testautomount incl 0
> umounted indirect mount /testautomount
> automount_path_to_fifo: fifo name /run/autofs.fifo-testautomount
> shut down path /testautomount
> autofs stopped
More information about the blfs-support