FS#12768 - [autofs] 5.0.4-1 unusable
Attached to Project:
Arch Linux
Opened by Jakub Schmidtke (sjakub) - Monday, 12 January 2009, 21:39 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 06 August 2009, 00:22 GMT
Opened by Jakub Schmidtke (sjakub) - Monday, 12 January 2009, 21:39 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 06 August 2009, 00:22 GMT
|
Details
autofs-5.0.4-1 is unusable - rc.d script is broken (or the
package is missing something):
- rc script uses "/usr/bin/automuonter" - mUOnter - Not only the spelling is probably wrong, this package doesn't contain any files in /usr/bin, the only executable is /usr/sbin/automount |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Thursday, 06 August 2009, 00:22 GMT
Reason for closing: Works for me
Thursday, 06 August 2009, 00:22 GMT
Reason for closing: Works for me
please try if there're problems with testing/autofs-5.0.4-2
PID=`cat /var/run/autofs-running &> /dev/null`
in the 5.0.4-2 version is complete bogus - PID is always empty as the value is always piped to null. It should look something along the lines of
[ -f /var/run/autofs-running ] && PID=`cat /var/run/autofs-running`
try to fix the typo:
PID=`cat /var/run/autofs-running 2> /dev/null`
In daemon.log:
Feb 2 21:54:41 hp510 automount[6737]: failed to mount /media/autofs/remote
Feb 2 21:54:41 hp510 automount[6737]: cannot find mount method for filesystem fuse
Feb 2 21:54:41 hp510 automount[6738]: failed to mount /media/autofs/sda4
Feb 2 21:54:41 hp510 automount[6738]: cannot find mount method for filesystem auto
My relevant autofs file:
sda4 -fstype=auto,defaults,noatime,iocharset=utf8,uid=1000 :/dev/sda4
remote -fstype=fuse,rw,nodev,nonempty,noatime,allow_other,max_read=65536 :sshfs\#someuser@somehost.org\:
Has the syntax changed? I do not think so. Can you reproduce it? If not, what could have gone wrong?
I also added the path to my master file in /etc/conf.d/autofs because of this bug report http://bugs.archlinux.org/task/12935
It works fine, and while I was at it I also added --debug to see under the hood - I mount dvd's, usb storage and many NFS shares with autofs and everything works ok with this upgrade.
FS#12935Should I consider this bug fixed in autofs-5.0.4-3?
It could print some error messages, or at least say 'FAIL' instead of 'DONE' while starting.
conf.d file contains localoptions variable that doesn't do anything.
The rc script is still wrong. Why do you start automount in the background?
It doesn't make any sense, plus you don't get correct error code if something (like run options)
is wrong!
Have you tested it at all?
what else?
Fixed rc.d file, remvoed localoptions from conf.d file.
Also auto.master defaults were wrong and used non existing /etc/auto.media file - fixed that.
And removed auto.net - it didn't make sense, autofs doesn't include showmount. If it is external package,
I don't see one (maybe it's part os some other package)? If it is supposed to be provided by some other package, it should be in autofs' optdepends.
I can't test it now. I made your changes in -4
There is now an easier syntax, see man auto.master for '-hosts' or http://bbs.archlinux.org/viewtopic.php?id=71219