Chapter 27 . Running a File Servers 727 (Tomcat web server)
Chapter 27 . Running a File Servers 727 . wsize The number of bytes of data written at a time to an NFS server. The default is 1,024. Performance issues are the same as with the rsize option. . timeo=# Sets the time after an RPC timeout occurs that a second transmission is made, where # represents a number in tenths of a second. The default value is seven-tenths of a second. Each successive timeout causes the timeout value to be doubled (up to 60 seconds maximum). Increase this value if you believe that timeouts are occurring because of slow response from the server or a slow network. . retrans=# Sets the number of minor timeouts and retransmissions that need to happen before a major timeout occurs. . retry=# Sets how many minutes to continue to retry failed mount requests, where # is replaced by the number of minutes to retry. The default is 10,000 minutes (which is about one week). . bg If the first mount attempt times out, try all subsequent mounts in the background. This option is very valuable if you are mounting a slow or sporadically available NFS file system. By placing mount requests in the background, your system can continue to mount other file systems instead of waiting for the current one to complete. If a nested mount point is missing, a timeout to allow for the needed mount point to be added occurs. For example, if you mount /usr/trip and /usr/trip/ extra as NFS file systems and /usr/trip is not yet mounted when /usr/ trip/extra tries to mount, /usr/trip/extra will time out. If you re lucky, /usr/trip comes up and /usr/trip/extra mounts on the next retry. . fg If the first mount attempt times out, try subsequent mounts in the foreground. This is the default behavior. Use this option if it is imperative that the mount be successful before continuing (for example, if you were mounting /usr). Any of the options that don t require a value can have no appended to it to have the opposite effect. For example, nobg indicates that the mount should not be done in the background. Using autofs to Mount NFS File Systems on Demand With the autofs facility configured and turned on, you can cause any NFS shared directories to mount on demand. To use the autofs facility, you need to have the autofs package installed. (For Fedora, you can type yum install autofs or for Debian type apt-get install autofs to install the package from the network.) With autofs enabled, if you know the host name and directory being shared by another host computer, simply change (cd) to the autofs mount directory (/net by default). This causes the shared resource to be automatically mounted and made accessible to you. Note
Please visit Domain Name Hosting services for high quality webhost to host and run your jsp applications.