Inside Linux (Web design service) The automounter is actually a collection
Inside Linux The automounter is actually a collection of individual components. Each of these components is critical to the success of the automounter. As can be expected, a daemon process is required and is called automountd. This daemon is the real workhorse, because it is the process that handles all the requests to the NFS server daemon process (nfsd). The second component is the automount command. The automount command is used to configure mount points for autofs. The automount command works using a base mount point and map, and uses this combination to automatically mount filesystems when they are accessed in any way. The third component is autofs, which is implemented as a virtual filesystem. The autofs command is used to control the automount daemons that are running on your Linux system; normally, autofs is executed at system boot. The following discussion describes the sequence of events for a “generic” automount start up -I will discuss automount as it applies to Linux. The automount command is executed at system start up. Next, automount reads the master configuration file named auto.master. After this point, if a user attempts to access a filesystem identified as a mount point, the autofs daemon calls on the services of the automount daemon, requesting that it mount the filesystem. The operation performed by the user can be something as simple as the cd or ls command. Next, the automount daemon tries to establish a conversation at the server side with nfsd, the NFS daemon. A lookup is performed in /etc/mnttab, searching for the requested path, server:/usr/bill/data using our example. After the path has been verified, the filesystem is mounted to the proper mount point -/mnt/data, using our example. Thus, the namespace is updated to include the new mount. NFS Server The NFS server has a fairly straightforward job - its focus is to provide access to its filesystems by NFS clients within the network. The NFS server makes the filesystems available to the world by exporting the filesystem(s). An exported filesystem is one that has been exported by the server and is available for access by NFS clients within the network. At system startup, a configuration file is read that contains information for exporting filesystems. Basically, the configuration file contains entries for each filesystem that is exported. The following list identifies the fields for each export entry: The directory pathname that is to be exported A list of client machines that will access the exported filesystem Access restrictions that might be required Both daemon processes, mountd and nfsd, after execution, sit and wait for requests (filesystem accesses) from NFS clients. NFS and Linux This section explores the world of NFS specific to the Linux operating system. After all, other operating systems are out there, and you want to be able to utilize those filesystems. You also want to share the filesystems found on your Linux systems, if that is a requirement. Linux is a natural choice for NFS support. You can use your Linux system as an NFS client, mounting remote filesystems (that are available) to your local filesystem. You can also offer your Linux system as an NFS server, allowing Linux clients to mount filesystems offered by your NFS server. Considering that Linux implements NFS in peer-to-peer mode, you can have the best of both worlds. Your Linux system can run as an NFS server sharing files to NFS clients, and your system can operate simultaneously as an NFS client. You should be sure to read the following section on security. As you know, NFS is a protocol for file sharing, which can create security issues. NFS is an open architecture that is known and understood by crackers; therefore, NFS offers another door through which crackers can gain access to your system. With all this said, let us begin our journey. page 214
We recommend high quality webhost to host and run your jsp application: christian web host services.