<?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 Tips for setting up NFS server on OpenVMS to be accessed by a Linux Box in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/tips-for-setting-up-nfs-server-on-openvms-to-be-accessed-by-a/m-p/3693403#M50946</link>
    <description>I have tried to collect some very useful tips for You who intent to host a web server on OpenVMS platform and want to do that with a Linux machine.&lt;BR /&gt;&lt;BR /&gt;First things first - get the latest patches. Especially get the latest patch for TCPIP and ESPECIALLY if You run OpenVMS V7.3-2. The TCPIP does not run flawlessely in an out-of-the-box installation.&lt;BR /&gt;&lt;BR /&gt;You could administer Your html with edit/tpu but for some reason I prefer using some WYSIWYG editor. As I am running a Linux workstation I use NWU. There might be some VMS based editors around but as I have this Linux thing ...&lt;BR /&gt;&lt;BR /&gt;The problem with non-VMS editors is the peculiar file names and especially the distinctive directory syntax of VMS. I have not seen any html editor that survives raw VMS directories not to talk about the protection settings.&lt;BR /&gt;&lt;BR /&gt;After several try-outs I succeeded quite well with sharing the VMS drive using NFS and mapping that into my Linux box.&lt;BR /&gt;&lt;BR /&gt;At first the NFS did not want to cooperate at all. There were several reasons for this:&lt;BR /&gt;- the TCPIP was the out-of-the-box version and it needed the patch to stop wobbling&lt;BR /&gt;- the host names ARE case sensitive. Always preserve case in ADD EXPORT, MAP and ADD PROXY commands by using double quotes around IP addresses&lt;BR /&gt;- check and double check the proxy settings. I have at least 300 grey hair-straws on top of my skull because of these.&lt;BR /&gt;- the Linux NFS client ALWAYS tries TCP protocol first unless You tell it not to. The TCP try-out confuses the OpenVMS NFS server and causes peculiar "RPC not available" messages.&lt;BR /&gt;&lt;BR /&gt;Here are the TCPIP settings for NFS server in my case:&lt;BR /&gt;&lt;BR /&gt;TCPIP&amp;gt; show map&lt;BR /&gt; Dynamic Filesystem Map&lt;BR /&gt;Pathname    Logical File System&lt;BR /&gt;/wwwdisk    AS2000$DKA500:&lt;BR /&gt;&lt;BR /&gt;TCPIP&amp;gt; show export&lt;BR /&gt;File System      Host name&lt;BR /&gt;/wwwdisk/wwwroot fragpc.furpile.com&lt;BR /&gt;       Options:  Purge Typeless Name_cvt&lt;BR /&gt;&lt;BR /&gt;TCPIP&amp;gt; show proxy&lt;BR /&gt;VMS User_name     Type      User_ID    Group_ID   Host_name&lt;BR /&gt;APACHE$WWW        OND           500         500   fragpc.furpile.com&lt;BR /&gt;SYSTEM            OND             0           1   fragpc.furpile.com&lt;BR /&gt;&lt;BR /&gt;Note the Options on the export.&lt;BR /&gt;The Purge will keep versions at one. When I got the mapping working I had a  lot of trouble with multiple file versions. The editor was not able to cope with them.&lt;BR /&gt;The Typeless rips off the .DIR from diorectory files. These were another source of trouble both for the editor and the Linux GUI which started acting strangely every time I opened a file dialog or tried to browse the files.&lt;BR /&gt;The Name_cvt is not needed if the volume has ODS-5 structure but it is essential for ODS-2 volumes. For ODS-5 volumes it is ignored.&lt;BR /&gt;&lt;BR /&gt;Since the APACHE$WWW is the default UIC for Apache on OpenVMS the proxy mapping converts my Linux GID/UID into that one and vice-versa. This simplifies things a lot as the web server ONLY sees files that are owned by APACHE$WWW or are granted for it. For this reason one has to check and double check that the wwwroot directory is owned by APACHE$WWW. If not - You will not be able to share it either with NFS (with these settings) or web server.&lt;BR /&gt;&lt;BR /&gt;In the linux side I found that the following line in /etc/fstab seemed to give the most reliable and efficient result:&lt;BR /&gt;as2000:/wwwdisk/wwwroot /mnt/wwwroot nfs rw,rsize=8192,wsize=8192,nolock,udp,hard,intr,vers=3&lt;BR /&gt;&lt;BR /&gt;Hopefully this gives some glues for those who are as nuts as I am. Having a half-size refridgerator (AlphaServer 2000 4/233) as web server under the desk. On the other hand - it  was the only machine that was still working after the multiple power failures during last summer thunder storms.&lt;BR /&gt;</description>
    <pubDate>Sat, 17 Dec 2005 00:06:10 GMT</pubDate>
    <dc:creator>Esko Ilola</dc:creator>
    <dc:date>2005-12-17T00:06:10Z</dc:date>
    <item>
      <title>Tips for setting up NFS server on OpenVMS to be accessed by a Linux Box</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tips-for-setting-up-nfs-server-on-openvms-to-be-accessed-by-a/m-p/3693403#M50946</link>
      <description>I have tried to collect some very useful tips for You who intent to host a web server on OpenVMS platform and want to do that with a Linux machine.&lt;BR /&gt;&lt;BR /&gt;First things first - get the latest patches. Especially get the latest patch for TCPIP and ESPECIALLY if You run OpenVMS V7.3-2. The TCPIP does not run flawlessely in an out-of-the-box installation.&lt;BR /&gt;&lt;BR /&gt;You could administer Your html with edit/tpu but for some reason I prefer using some WYSIWYG editor. As I am running a Linux workstation I use NWU. There might be some VMS based editors around but as I have this Linux thing ...&lt;BR /&gt;&lt;BR /&gt;The problem with non-VMS editors is the peculiar file names and especially the distinctive directory syntax of VMS. I have not seen any html editor that survives raw VMS directories not to talk about the protection settings.&lt;BR /&gt;&lt;BR /&gt;After several try-outs I succeeded quite well with sharing the VMS drive using NFS and mapping that into my Linux box.&lt;BR /&gt;&lt;BR /&gt;At first the NFS did not want to cooperate at all. There were several reasons for this:&lt;BR /&gt;- the TCPIP was the out-of-the-box version and it needed the patch to stop wobbling&lt;BR /&gt;- the host names ARE case sensitive. Always preserve case in ADD EXPORT, MAP and ADD PROXY commands by using double quotes around IP addresses&lt;BR /&gt;- check and double check the proxy settings. I have at least 300 grey hair-straws on top of my skull because of these.&lt;BR /&gt;- the Linux NFS client ALWAYS tries TCP protocol first unless You tell it not to. The TCP try-out confuses the OpenVMS NFS server and causes peculiar "RPC not available" messages.&lt;BR /&gt;&lt;BR /&gt;Here are the TCPIP settings for NFS server in my case:&lt;BR /&gt;&lt;BR /&gt;TCPIP&amp;gt; show map&lt;BR /&gt; Dynamic Filesystem Map&lt;BR /&gt;Pathname    Logical File System&lt;BR /&gt;/wwwdisk    AS2000$DKA500:&lt;BR /&gt;&lt;BR /&gt;TCPIP&amp;gt; show export&lt;BR /&gt;File System      Host name&lt;BR /&gt;/wwwdisk/wwwroot fragpc.furpile.com&lt;BR /&gt;       Options:  Purge Typeless Name_cvt&lt;BR /&gt;&lt;BR /&gt;TCPIP&amp;gt; show proxy&lt;BR /&gt;VMS User_name     Type      User_ID    Group_ID   Host_name&lt;BR /&gt;APACHE$WWW        OND           500         500   fragpc.furpile.com&lt;BR /&gt;SYSTEM            OND             0           1   fragpc.furpile.com&lt;BR /&gt;&lt;BR /&gt;Note the Options on the export.&lt;BR /&gt;The Purge will keep versions at one. When I got the mapping working I had a  lot of trouble with multiple file versions. The editor was not able to cope with them.&lt;BR /&gt;The Typeless rips off the .DIR from diorectory files. These were another source of trouble both for the editor and the Linux GUI which started acting strangely every time I opened a file dialog or tried to browse the files.&lt;BR /&gt;The Name_cvt is not needed if the volume has ODS-5 structure but it is essential for ODS-2 volumes. For ODS-5 volumes it is ignored.&lt;BR /&gt;&lt;BR /&gt;Since the APACHE$WWW is the default UIC for Apache on OpenVMS the proxy mapping converts my Linux GID/UID into that one and vice-versa. This simplifies things a lot as the web server ONLY sees files that are owned by APACHE$WWW or are granted for it. For this reason one has to check and double check that the wwwroot directory is owned by APACHE$WWW. If not - You will not be able to share it either with NFS (with these settings) or web server.&lt;BR /&gt;&lt;BR /&gt;In the linux side I found that the following line in /etc/fstab seemed to give the most reliable and efficient result:&lt;BR /&gt;as2000:/wwwdisk/wwwroot /mnt/wwwroot nfs rw,rsize=8192,wsize=8192,nolock,udp,hard,intr,vers=3&lt;BR /&gt;&lt;BR /&gt;Hopefully this gives some glues for those who are as nuts as I am. Having a half-size refridgerator (AlphaServer 2000 4/233) as web server under the desk. On the other hand - it  was the only machine that was still working after the multiple power failures during last summer thunder storms.&lt;BR /&gt;</description>
      <pubDate>Sat, 17 Dec 2005 00:06:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tips-for-setting-up-nfs-server-on-openvms-to-be-accessed-by-a/m-p/3693403#M50946</guid>
      <dc:creator>Esko Ilola</dc:creator>
      <dc:date>2005-12-17T00:06:10Z</dc:date>
    </item>
  </channel>
</rss>

