<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NFS in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/nfs/m-p/4097664#M83226</link>
    <description>An NFS server on linux requires 3 services to be running in order to share files:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/etc/rc.d/init.d/portmap&lt;BR /&gt;/etc/rc.d/init.d/nfslock&lt;BR /&gt;/etc/rc.d/init.d/nfs&lt;BR /&gt;&lt;BR /&gt;You can start/stop/restart these services by issues the above lines with the corresponding arguments: start, stop or restart. You can also use the shortcut 'service' command, as in:&lt;BR /&gt;&lt;BR /&gt;# service portmap start&lt;BR /&gt;&lt;BR /&gt;You need to ensure that these 3 services start up when the system does.&lt;BR /&gt;&lt;BR /&gt;First, verify the default runlevel of the computer. Check the line in /etc/inittab that starts with "id:". The next number will be the default runlevel (usually 3 for non-gui, 5 for gui). You can manage the startup scripts manually by creating symlinks in the corresponding /etc/rc.d/rcX.d directory (where X is the default runlevel) or you can use redhat's "chkconfig" command. Assuming the default runlevel is 3, these 3 commands will ensure that the services necessary for an nfs server start at boot time (these all must run as root):&lt;BR /&gt;&lt;BR /&gt;# chkconfig --level 3 portmap on&lt;BR /&gt;# chkconfig --level 3 nfslock on&lt;BR /&gt;# chkconfig --level 3 nfs on&lt;BR /&gt;&lt;BR /&gt;Now either reboot the box or issue these commands to start the nfs server:&lt;BR /&gt;&lt;BR /&gt;# service nfs stop&lt;BR /&gt;# service nfslock stop&lt;BR /&gt;# service portmap stop&lt;BR /&gt;# service portmap start&lt;BR /&gt;# service nfslock start&lt;BR /&gt;# service nfs start&lt;BR /&gt;&lt;BR /&gt;Order is important. Portmap must start first, followed by nfslock, followed by nfs.&lt;BR /&gt;&lt;BR /&gt;The file that defines what directories are shared is /etc/exports. 'man exports' will give you the full overview of all options available for this file. Here is an example line:&lt;BR /&gt;&lt;BR /&gt;/public *(rw,no_root_squash)&lt;BR /&gt;&lt;BR /&gt;This says share the folder /public, allow any IP access, give read/write access, and allow the root user to connect as root.&lt;BR /&gt;&lt;BR /&gt;The * wildcard can be a list or range of IP addresses. For example, if we wanted to restrict this access to the 192.168.1.0/24 Class C subnet, the line would look like this:&lt;BR /&gt;&lt;BR /&gt;/public 192.168.1.0/255.255.255.0(rw,no_root_squash)&lt;BR /&gt;&lt;BR /&gt;rw means read/write. no_root_squash is a setting that allows nfs clients to connect as root. Without this setting, the root user on clients that connect has the permissions of the user 'nfsnobody', uid 65534.&lt;BR /&gt;&lt;BR /&gt;Anytime you make any changes to the /etc/exports file, run the command:&lt;BR /&gt;&lt;BR /&gt;# exportfs -avr&lt;BR /&gt;on the server to update the nfs server.</description>
    <pubDate>Wed, 14 Nov 2007 00:02:59 GMT</pubDate>
    <dc:creator>sandeep mathur</dc:creator>
    <dc:date>2007-11-14T00:02:59Z</dc:date>
    <item>
      <title>NFS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nfs/m-p/4097662#M83224</link>
      <description>Please send me the procedure for NFS configure in linux .</description>
      <pubDate>Mon, 05 Nov 2007 23:59:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nfs/m-p/4097662#M83224</guid>
      <dc:creator>Ping problem</dc:creator>
      <dc:date>2007-11-05T23:59:29Z</dc:date>
    </item>
    <item>
      <title>Re: NFS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nfs/m-p/4097663#M83225</link>
      <description>There are many HOW-TOs for NFS configuration. If you search for "NFS configuration" in Google, you will find many relevant results. I found this (independent of which Linux Distro you are using):&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://nfs.sourceforge.net/nfs-howto/" target="_blank"&gt;http://nfs.sourceforge.net/nfs-howto/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Good Luck!</description>
      <pubDate>Tue, 06 Nov 2007 00:20:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nfs/m-p/4097663#M83225</guid>
      <dc:creator>~sesh</dc:creator>
      <dc:date>2007-11-06T00:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: NFS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nfs/m-p/4097664#M83226</link>
      <description>An NFS server on linux requires 3 services to be running in order to share files:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/etc/rc.d/init.d/portmap&lt;BR /&gt;/etc/rc.d/init.d/nfslock&lt;BR /&gt;/etc/rc.d/init.d/nfs&lt;BR /&gt;&lt;BR /&gt;You can start/stop/restart these services by issues the above lines with the corresponding arguments: start, stop or restart. You can also use the shortcut 'service' command, as in:&lt;BR /&gt;&lt;BR /&gt;# service portmap start&lt;BR /&gt;&lt;BR /&gt;You need to ensure that these 3 services start up when the system does.&lt;BR /&gt;&lt;BR /&gt;First, verify the default runlevel of the computer. Check the line in /etc/inittab that starts with "id:". The next number will be the default runlevel (usually 3 for non-gui, 5 for gui). You can manage the startup scripts manually by creating symlinks in the corresponding /etc/rc.d/rcX.d directory (where X is the default runlevel) or you can use redhat's "chkconfig" command. Assuming the default runlevel is 3, these 3 commands will ensure that the services necessary for an nfs server start at boot time (these all must run as root):&lt;BR /&gt;&lt;BR /&gt;# chkconfig --level 3 portmap on&lt;BR /&gt;# chkconfig --level 3 nfslock on&lt;BR /&gt;# chkconfig --level 3 nfs on&lt;BR /&gt;&lt;BR /&gt;Now either reboot the box or issue these commands to start the nfs server:&lt;BR /&gt;&lt;BR /&gt;# service nfs stop&lt;BR /&gt;# service nfslock stop&lt;BR /&gt;# service portmap stop&lt;BR /&gt;# service portmap start&lt;BR /&gt;# service nfslock start&lt;BR /&gt;# service nfs start&lt;BR /&gt;&lt;BR /&gt;Order is important. Portmap must start first, followed by nfslock, followed by nfs.&lt;BR /&gt;&lt;BR /&gt;The file that defines what directories are shared is /etc/exports. 'man exports' will give you the full overview of all options available for this file. Here is an example line:&lt;BR /&gt;&lt;BR /&gt;/public *(rw,no_root_squash)&lt;BR /&gt;&lt;BR /&gt;This says share the folder /public, allow any IP access, give read/write access, and allow the root user to connect as root.&lt;BR /&gt;&lt;BR /&gt;The * wildcard can be a list or range of IP addresses. For example, if we wanted to restrict this access to the 192.168.1.0/24 Class C subnet, the line would look like this:&lt;BR /&gt;&lt;BR /&gt;/public 192.168.1.0/255.255.255.0(rw,no_root_squash)&lt;BR /&gt;&lt;BR /&gt;rw means read/write. no_root_squash is a setting that allows nfs clients to connect as root. Without this setting, the root user on clients that connect has the permissions of the user 'nfsnobody', uid 65534.&lt;BR /&gt;&lt;BR /&gt;Anytime you make any changes to the /etc/exports file, run the command:&lt;BR /&gt;&lt;BR /&gt;# exportfs -avr&lt;BR /&gt;on the server to update the nfs server.</description>
      <pubDate>Wed, 14 Nov 2007 00:02:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nfs/m-p/4097664#M83226</guid>
      <dc:creator>sandeep mathur</dc:creator>
      <dc:date>2007-11-14T00:02:59Z</dc:date>
    </item>
  </channel>
</rss>

