| Summary: | autofs doesn't work with /etc/autofs/auto.net | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Luca Olivetti <luca> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, remco |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | autofs-5.0.5-4.mga1.src.rpm | CVE: | |
| Status comment: | |||
Hi, thanks for reporting this bug. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it) Keywords:
(none) =>
Triaged I tried the binary package from mandriva 2010.2 that works on the mandriva machine (both the x86_64 and the i586 version, since this one is x86_64 but the mandriva one is i586) and the result is the same, so maybe the problem is in the kernel and not in the automounter. I will attempt NFS automounting soon - tonight i only browsed the net, found this bug, installed autofs and read the upgrading info that drakrpm provided as below: Luca: Are you configuring using the correct files? To developers: I presume Mandriva should be changed to Mageia? (and polish the english) Mandriva RPM specific notes setup ----- Configuration handling in Mandriva package differs from upstream one on several points: - the automounts daemon configuration file is /etc/autofs/autofs.conf - the autofs service configuration file is /etc/sysconfig/autofs - the configuration directives in /etc/autofs/autofs.conf don't have the 'DEFAULT_' prefix (for instance, DEFAULT_TIMEOUT is just TIMEOUT). This has recently been changed upstream in version 5.0.2 too, but given than documentation still refers to old names Upgrade ------- Map files have been moved from /etc to /etc/autofs. Upgrade procedure should handle the change automatically. LDAP usage has changed between autofs 4 and 5. The LDAP schema used has now to be configured explicitely in autofs configuration, so as to avoid useless queries. As this can't be handled by package upgrade procedure, you'll have to edit your configuration manually. See auto.master(5) for details. CC:
(none) =>
fri (In reply to comment #3) > > Luca: Are you configuring using the correct files? Yes, just look at the title of this bug. Luca, Can you try with putting the file as /etc/auto.net instead of /etc/autofs/auto.net and see if it works then? CC:
(none) =>
remco It doesn't make a difference (the location of the executable map is specified in /etc/autofs/auto.master, so it doesn't really matter where it is). Reassigning to bugsquad as we have no pulse on the maintainer... Luca, are you able to test if this is still an issue with Mageia 2 and/or Cauldron? (This because the changes between the versions shipped in 1 and 2 are quite extensive) Keywords:
Triaged =>
(none) No, sorry, I'm swamped. I installed mageia 2 in virtualbox and it works OK (though I used the i586 version instead of x86_64). Tested OK also with x86_64. BTW, the default /etc/autofs/auto.master references the /etc/auto.master.d directory which isn't there (and in any case it should probably be /etc/autofs/auto.master.d). This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
NEW =>
RESOLVED |
I'm trying to use autofs to mount on demand from an nfs server. The same, simple, configuration is working on mandriva 2010.0 and 2010.2 but not on mageia 1. In /etc/autofs/auto.master I just put /net /etc/autofs/auto.net --timeout=60 If I run automount on the foreground on the mandriva machine, this is what I see when I try to ls /net/pippo: # automount -f -v Starting automounter version 5.0.5, master map auto.master using kernel protocol version 5.01 mounted indirect on /net with timeout 60, freq 15 seconds ghosting enabled attempting to mount entry /net/pippo mounted offset on /net/pippo/home with timeout 60, freq 15 seconds mounted /net/pippo On the mageia 1 machine I just get a file not found reply to ls /net/pippo and I see no attempt to mount from automount: # automount -f -v -v Starting automounter version 5.0.5, master map auto.master using kernel protocol version 5.02 mounted indirect on /net with timeout 60, freq 15 seconds ghosting enabled The output of "/etc/autofs/auto.net pippo" is the same on both machines: -fstype=nfs,hard,intr,nodev,nosuid \ /home pippo:/home As a workaround I used /net -hosts and put the address of the server I need to mount from in /etc/hosts