Automount is a service on most Linux computers which allows directories (usually from a remote server using NFS) to be mounted on the client when required. If a directory is not used for a time then it will be unmounted from the client.<\/p>\n
Automounting is based on maps which detail the mounts that can be made in a particular directory. These maps can be either stored in local files on the client or in some Name Information Service such as NIS (aka yp) or LDAP.<\/p>\n Most maps will have a large number of entries, so to improve efficiency, they will have browsing turned off. This means that when you list the contents of the automount directory (e.g. \/home<\/span>\u00a0) you will only see the directories that have been mounted. This also means that file completion does not work on automount directories so \/home\/users\/ma<\/span>\u00a0<tab> will not expand to \/home\/user\/mary<\/span><\/p>\n There is a special automount map which is used to mount directories exported from a server. So the user mary’s home directory could be accessed as \/net\/nas4.example.com\/export\/home2\/mary<\/span>\u00a0.<\/p>\n However there are some drawbacks in using \/net<\/span> <\/p>\n","protected":false},"excerpt":{"rendered":" Automount is a service on most Linux computers which allows directories (usually from a remote server using NFS) to be mounted on the client when required. If a directory is not used for a time then it will be unmounted from the client. Automount Maps Automounting is based on maps which detail the<\/p>\n","protected":false},"author":361,"featured_media":1008,"template":"","meta":{"_acf_changed":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"__cvm_playback_settings":[],"__cvm_video_id":"","_links_to":"","_links_to_target":""},"kbe_taxonomy":[61],"kbe_tags":[],"class_list":["post-1279","kbe_knowledgebase","type-kbe_knowledgebase","status-publish","has-post-thumbnail","hentry","kbe_taxonomy-academic-cluster-articles"],"acf":[],"yoast_head":"\n
\nFor example there may be a map for home directories (usually called auto.home) which will detail the server and the location on that server of a users home directory to be mounted under \/home\/users<\/span>\u00a0.
\nSo the user mary’s home directory maybe in \/export\/home2\/mary<\/span>\u00a0 on server nas4.example.com and this will be mounted on \/home\/users\/mary<\/span>\u00a0.<\/p>\nBrowsing<\/h2>\n
\nTo see a particular mount you have to reference it explicitly (e.g.\/home\/users\/mary<\/span>\u00a0)<\/p>\n\/net<\/h2>\n
\n* The user need to know server and the location on that server of the directory they want to access. Because this information is known to users it makes it more difficult for administrators to manage the data and servers.
\n* When a server is referenced (e.g \/net\/nas4.example.com<\/span>\u00a0) all of the exports that the client is allowed to access are mounted. This places an extra load on the client and the server.
\n* Any new exports on the server will not be visible under \/net<\/span>\u00a0 until all current mounts for that server under \/net<\/span>\u00a0 have been unmounted.<\/p>\n