Comment 21 for bug 683938
Revision history for this message
| Thomas Bushnell, BSG (tbushnell) wrote | #21 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
An interesting (possible) data point. The bug does not happen if the automount fails because the target directory doesn't exist, or because the server hostname is wrong (*). It seems that if you have an automount which fails for such a reason, and then you switch to the permission-denied mount (on the same name) you also don't get the bug.
(*): This is quite odd, btw. If the hostname doesn't exist, then the automounter doesn't even attempt the mount command, but if the directory is wrong, then it does attempt the mount command, and seemingly gets exactly the same error from the server, but it doesn't crash.