Re: NFS question on statd and lockd ports ....
Thanks for the responses. I just received another response from Neil: > > I noticed that when I set the lockd ports to specific port that the statd > port is set to the same port. This behavior is specific to SLES9 and SLES10. The kernels in those distributions contain statd functionality and use the same port as lockd uses. > > Should I also set statd to a specific unique port different from lockd ? > You cannot in SLES9/10. On other systems where statd is a user-space program, they cannot be the same port. > Is there any problem with statd using the same port as lockd ? Not on SLES9/10. - Alan responds: I think this will cause one of them to fail to function. You can't actually have two processes bind to one port. Even if you could, only one of them would get the connection. This might result in the client lock request going to the statd, or the client status request going to the lockd. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Terry Spaulding Sent: Thursday, August 30, 2007 9:56 AM To: LINUX-390@VM.MARIST.EDU Subject: NFS question on statd and lockd ports I have posted this question to : [EMAIL PROTECTED] with no response yet. Any assistance on this would be appreciated. I noticed that when I set the lockd (lockmngr) ports to a specific static port that the statd (status) port is set to the same port. Regards, Terry L. Spaulding [EMAIL PROTECTED] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: NFS question on statd and lockd ports ....
I think this will cause one of them to fail to function. You can't actually have two processes bind to one port. Even if you could, only one of them would get the connection. This might result in the client lock request going to the statd, or the client status request going to the lockd. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Terry Spaulding Sent: Thursday, August 30, 2007 9:56 AM To: LINUX-390@VM.MARIST.EDU Subject: NFS question on statd and lockd ports I have posted this question to : [EMAIL PROTECTED] with no response yet. Any assistance on this would be appreciated. I noticed that when I set the lockd (lockmngr) ports to a specific static port that the statd (status) port is set to the same port. Should I also set statd (status) to a specific unique port different from the lockd (lockmngr) port ? Is there any problem with statd (status) using the same port as lockd (lockmngr) ? SLES9 SP3 plus maintenance. My current NFS Server: linux01:/ # rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 152 udp 6001 mountd 152 tcp 6001 mountd 153 udp 6001 mountd 153 tcp 6001 mountd 132 udp 2049 nfs 133 udp 2049 nfs 1002273 udp 2049 nfs_acl 132 tcp 2049 nfs 133 tcp 2049 nfs 1002273 tcp 2049 nfs_acl 1000241 udp 6002 status 1000211 udp 6002 nlockmgr 1000213 udp 6002 nlockmgr 1000214 udp 6002 nlockmgr 1000241 tcp 6002 status 1000211 tcp 6002 nlockmgr 1000213 tcp 6002 nlockmgr 1000214 tcp 6002 nlockmgr 151 udp 6001 mountd linux01:/ # NFS Client: linux02:~ # rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 1000241 udp 6002 status 1000211 udp 6002 nlockmgr 1000213 udp 6002 nlockmgr 1000214 udp 6002 nlockmgr 1000241 tcp 6002 status 1000211 tcp 6002 nlockmgr 1000213 tcp 6002 nlockmgr 1000214 tcp 6002 nlockmgr linux02:~ # tia Regards, Terry L. Spaulding [EMAIL PROTECTED] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
NFS question on statd and lockd ports ....
I have posted this question to : [EMAIL PROTECTED] with no response yet. Any assistance on this would be appreciated. I noticed that when I set the lockd (lockmngr) ports to a specific static port that the statd (status) port is set to the same port. Should I also set statd (status) to a specific unique port different from the lockd (lockmngr) port ? Is there any problem with statd (status) using the same port as lockd (lockmngr) ? SLES9 SP3 plus maintenance. My current NFS Server: linux01:/ # rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 152 udp 6001 mountd 152 tcp 6001 mountd 153 udp 6001 mountd 153 tcp 6001 mountd 132 udp 2049 nfs 133 udp 2049 nfs 1002273 udp 2049 nfs_acl 132 tcp 2049 nfs 133 tcp 2049 nfs 1002273 tcp 2049 nfs_acl 1000241 udp 6002 status 1000211 udp 6002 nlockmgr 1000213 udp 6002 nlockmgr 1000214 udp 6002 nlockmgr 1000241 tcp 6002 status 1000211 tcp 6002 nlockmgr 1000213 tcp 6002 nlockmgr 1000214 tcp 6002 nlockmgr 151 udp 6001 mountd linux01:/ # NFS Client: linux02:~ # rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 1000241 udp 6002 status 1000211 udp 6002 nlockmgr 1000213 udp 6002 nlockmgr 1000214 udp 6002 nlockmgr 1000241 tcp 6002 status 1000211 tcp 6002 nlockmgr 1000213 tcp 6002 nlockmgr 1000214 tcp 6002 nlockmgr linux02:~ # tia Regards, Terry L. Spaulding [EMAIL PROTECTED] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: RHEL 4 NFS question
SFS (shared file system) is a file system unique to VM, VM also has BFS (byte file system) and of course, minidisks. Information is stored on minidisks (mdisks) and SFS in the same format, i.e, you can copy a file from SFS to/from mdisks with a copy command. BFS uses different commands. Each FS has it's pros and cons. NFS allows access to any of these file types. I've used NFS to read/write to all three of these storage methods, but NFS seems to work better or is more friendly towards SFS and BFS (in my opinion). I have an app. that I copy files from a mdisk to SFS and then use NFS (aka VMNFS) so I can issue a mount command from linux and copy the files to that linux. Works great; getting the security right can be a little tricky. Steve G. Brad Hinson <[EMAIL PROTECTED]> Sent by: Linux on 390 Port 05/14/2007 04:31 PM Please respond to Linux on 390 Port To: LINUX-390@VM.MARIST.EDU cc: Subject: Re: RHEL 4 NFS question I haven't heard much about SFS; Is this basically NFS for VM? Just to eliminate some unknowns, try: # service iptables stop # setenforce 0 and retry the mount. This will stop the firewall (iptables) and temporarily disable SELinux. It also may be helpful to look at a network trace (tcpdump) of the NFS traffic. I can shoot you a note offline on how to set this up if the above doesn't work for you. -Brad On Mon, 2007-05-14 at 13:02 -0700, Spann, Elizebeth (Betsie) wrote: > The dmesg display has no reference to 'firewall'. What should I be > looking for, please? > B > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Mark Post > Sent: Monday, May 14, 2007 12:21 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: RHEL 4 NFS question > > >>> On Mon, May 14, 2007 at 1:53 PM, in message > <[EMAIL PROTECTED]>, "Spann, > Elizebeth (Betsie)" <[EMAIL PROTECTED]> wrote: > > Hi Linux exports, > > Oh, man, do I have to start worrying about export controls now? ;) > > > In converting a SuSE SLES 9 server to RHEL AS 4, I cannot mount a SFS > > running on another VM system. > > The VMNFS server on the other VM system does not restrict exports. > > The SFS files can be mounted on the SLES 9 systems, and on the VM > > system running the zLinux guests. > > The RHEL server can NFS mount exported files on other zLinux systems. > > Pings are successful by IP and hostname in all directions. > > > > The message is > > mount: trying 10.55.27.91 prog 13 vers 3 prot tcp port 2049 > > mount: mount to NFS server 'vm3' failed: timed out (retrying). > > Just a shot in the dark, but what does the firewall on the RHEL system > say about this, via the dmesg command? > > -snip- > > Anyone have any suggestions, please? > > Stick with what works? =:O (Sorry, couldn't resist.) > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Brad Hinson <[EMAIL PROTECTED]> Technical Account Manager Red Hat, Inc. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: RHEL 4 NFS question
Spann, Elizebeth (Betsie) wrote: The dmesg display has no reference to 'firewall'. What should I be looking for, please? Messages vaguely like this (one line): IN=ppp0 OUT= MAC= SRC=60.12.166.2 DST=220.235.39.228 LEN=490 TOS=0x00 PREC=0xE0 TTL=50 ID=0 DF PROTO=UDP SPT=40816 DPT=1026 LEN=470 They are generated when iptables logs traffic, and hopefully it's told to log everything it drops. When you have a moment to spare for education, man iptables and http://www.netfilter.org B -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, May 14, 2007 12:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL 4 NFS question On Mon, May 14, 2007 at 1:53 PM, in message <[EMAIL PROTECTED]>, "Spann, Elizebeth (Betsie)" <[EMAIL PROTECTED]> wrote: Hi Linux exports, Oh, man, do I have to start worrying about export controls now? ;) In converting a SuSE SLES 9 server to RHEL AS 4, I cannot mount a SFS running on another VM system. The VMNFS server on the other VM system does not restrict exports. The SFS files can be mounted on the SLES 9 systems, and on the VM system running the zLinux guests. The RHEL server can NFS mount exported files on other zLinux systems. Pings are successful by IP and hostname in all directions. The message is mount: trying 10.55.27.91 prog 13 vers 3 prot tcp port 2049 mount: mount to NFS server 'vm3' failed: timed out (retrying). Just a shot in the dark, but what does the firewall on the RHEL system say about this, via the dmesg command? -snip- Anyone have any suggestions, please? Stick with what works? =:O (Sorry, couldn't resist.) Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: RHEL 4 NFS question
I haven't heard much about SFS; Is this basically NFS for VM? Just to eliminate some unknowns, try: # service iptables stop # setenforce 0 and retry the mount. This will stop the firewall (iptables) and temporarily disable SELinux. It also may be helpful to look at a network trace (tcpdump) of the NFS traffic. I can shoot you a note offline on how to set this up if the above doesn't work for you. -Brad On Mon, 2007-05-14 at 13:02 -0700, Spann, Elizebeth (Betsie) wrote: > The dmesg display has no reference to 'firewall'. What should I be > looking for, please? > B > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Mark Post > Sent: Monday, May 14, 2007 12:21 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: RHEL 4 NFS question > > >>> On Mon, May 14, 2007 at 1:53 PM, in message > <[EMAIL PROTECTED]>, "Spann, > Elizebeth (Betsie)" <[EMAIL PROTECTED]> wrote: > > Hi Linux exports, > > Oh, man, do I have to start worrying about export controls now? ;) > > > In converting a SuSE SLES 9 server to RHEL AS 4, I cannot mount a SFS > > running on another VM system. > > The VMNFS server on the other VM system does not restrict exports. > > The SFS files can be mounted on the SLES 9 systems, and on the VM > > system running the zLinux guests. > > The RHEL server can NFS mount exported files on other zLinux systems. > > Pings are successful by IP and hostname in all directions. > > > > The message is > > mount: trying 10.55.27.91 prog 13 vers 3 prot tcp port 2049 > > mount: mount to NFS server 'vm3' failed: timed out (retrying). > > Just a shot in the dark, but what does the firewall on the RHEL system > say about this, via the dmesg command? > > -snip- > > Anyone have any suggestions, please? > > Stick with what works? =:O (Sorry, couldn't resist.) > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Brad Hinson <[EMAIL PROTECTED]> Technical Account Manager Red Hat, Inc. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: RHEL 4 NFS question
The dmesg display has no reference to 'firewall'. What should I be looking for, please? B -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, May 14, 2007 12:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL 4 NFS question >>> On Mon, May 14, 2007 at 1:53 PM, in message <[EMAIL PROTECTED]>, "Spann, Elizebeth (Betsie)" <[EMAIL PROTECTED]> wrote: > Hi Linux exports, Oh, man, do I have to start worrying about export controls now? ;) > In converting a SuSE SLES 9 server to RHEL AS 4, I cannot mount a SFS > running on another VM system. > The VMNFS server on the other VM system does not restrict exports. > The SFS files can be mounted on the SLES 9 systems, and on the VM > system running the zLinux guests. > The RHEL server can NFS mount exported files on other zLinux systems. > Pings are successful by IP and hostname in all directions. > > The message is > mount: trying 10.55.27.91 prog 13 vers 3 prot tcp port 2049 > mount: mount to NFS server 'vm3' failed: timed out (retrying). Just a shot in the dark, but what does the firewall on the RHEL system say about this, via the dmesg command? -snip- > Anyone have any suggestions, please? Stick with what works? =:O (Sorry, couldn't resist.) Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: RHEL 4 NFS question
>>> On Mon, May 14, 2007 at 1:53 PM, in message <[EMAIL PROTECTED]>, "Spann, Elizebeth (Betsie)" <[EMAIL PROTECTED]> wrote: > Hi Linux exports, Oh, man, do I have to start worrying about export controls now? ;) > In converting a SuSE SLES 9 server to RHEL AS 4, I cannot mount a SFS > running on another VM system. > The VMNFS server on the other VM system does not restrict exports. > The SFS files can be mounted on the SLES 9 systems, and on the VM system > running the zLinux guests. > The RHEL server can NFS mount exported files on other zLinux systems. > Pings are successful by IP and hostname in all directions. > > The message is > mount: trying 10.55.27.91 prog 13 vers 3 prot tcp port 2049 > mount: mount to NFS server 'vm3' failed: timed out (retrying). Just a shot in the dark, but what does the firewall on the RHEL system say about this, via the dmesg command? -snip- > Anyone have any suggestions, please? Stick with what works? =:O (Sorry, couldn't resist.) Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
RHEL 4 NFS question
Hi Linux exports, In converting a SuSE SLES 9 server to RHEL AS 4, I cannot mount a SFS running on another VM system. The VMNFS server on the other VM system does not restrict exports. The SFS files can be mounted on the SLES 9 systems, and on the VM system running the zLinux guests. The RHEL server can NFS mount exported files on other zLinux systems. Pings are successful by IP and hostname in all directions. The message is mount: trying 10.55.27.91 prog 13 vers 3 prot tcp port 2049 mount: mount to NFS server 'vm3' failed: timed out (retrying). [EMAIL PROTECTED] etc]# rpcinfo -t vm3 nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting >From the remote VM system: <> Anyone have any suggestions, please? Betsie -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 <>
Re: NFS question
If you only want to mount mvs hfs files, I think you only need tcpip, portmap and the nfs server address spaces. You don't need NAMESRV. [EMAIL PROTECTED] wrote: As you expected, portmapper failed. I am off to read "TCP/IP for MVS: Customization and Administration Guide" to see what I need to do to configure and start portmap. There is a reference to configuring the Domain Name Server and starting NAMESRV right after the information about portmap. Should I get that started too? *** EZA4329E orpcinfo: can't contact portmapper: EZA4339E RPC: Remote system error - EDC8128I Connection refused. -Original Message- From: Michael Morgan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 10:48 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question That's a good manual. In the beginning of chapter 5, it says to start portmap. What does the command: rpcinfo -p mvs_system show, where mvs_system is your mvs host name? [EMAIL PROTECTED] wrote: If it is on by default, but I did not start PORTMAP. I just configured NFS based on the "z/OS Network File System Customization and Operation" manual. Is there a better manual to reference the installation of NFS? Also, can someone point me to where I can see syslogd? I don't know if there is any information there but I can't say I have ever looked at it. -Original Message- From: Michael Morgan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 10:10 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question The message indicating that port 2049 was not registered is an error. Do you have the PORTMAP address space started? ..thanks [EMAIL PROTECTED] wrote: When I start mvsnfs, there are no filesystems exported to be mounted I copied the following text from my system log file, but I can't see any error messages detailing what problem I am having. GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - VERSION 2 - FAILED. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 8:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question When I did it years ago, it seemed pretty straightforward. I wouldn't think it would have gotten more complicated with z/OS, but I could be wrong. What exactly are the symptoms you're seeing? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 09, 2005 6:06 PM To: LINUX-390@VM.MARIST.EDU Subject: NFS question I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the "z/OS V1R2. Network File Systems Customization and Operations" manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the mess
Re: NFS question
As you expected, portmapper failed. I am off to read "TCP/IP for MVS: Customization and Administration Guide" to see what I need to do to configure and start portmap. There is a reference to configuring the Domain Name Server and starting NAMESRV right after the information about portmap. Should I get that started too? *** EZA4329E orpcinfo: can't contact portmapper: EZA4339E RPC: Remote system error - EDC8128I Connection refused. -Original Message- From: Michael Morgan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 10:48 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question That's a good manual. In the beginning of chapter 5, it says to start portmap. What does the command: rpcinfo -p mvs_system show, where mvs_system is your mvs host name? [EMAIL PROTECTED] wrote: > If it is on by default, but I did not start PORTMAP. I just > configured NFS based on the "z/OS Network File System Customization > and Operation" manual. Is there a better manual to reference the > installation of NFS? > > Also, can someone point me to where I can see syslogd? I don't know > if there is any information there but I can't say I have ever looked > at it. > > > > -Original Message- > From: Michael Morgan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 10, 2005 10:10 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: NFS question > > > The message indicating that port 2049 was not registered is an error. > Do you have the PORTMAP address space started? ..thanks > > [EMAIL PROTECTED] wrote: > > >>When I start mvsnfs, there are no filesystems exported to be mounted >> >>I copied the following text from my system log file, but I can't see >>any error messages detailing what problem I am having. >> >>GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) >>STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - >>VERSION 2 - FAILED. >> >>-Original Message- >>From: Post, Mark K [mailto:[EMAIL PROTECTED] >>Sent: Tuesday, May 10, 2005 8:02 AM >>To: LINUX-390@VM.MARIST.EDU >>Subject: Re: NFS question >> >> >>When I did it years ago, it seemed pretty straightforward. I wouldn't >>think it would have gotten more complicated with z/OS, but I could be >>wrong. >> >>What exactly are the symptoms you're seeing? >> >> >>Mark Post >> >>-Original Message- >>From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of >>[EMAIL PROTECTED] >>Sent: Monday, May 09, 2005 6:06 PM >>To: LINUX-390@VM.MARIST.EDU >>Subject: NFS question >> >> >>I want to setup under Linux the ability to mount an hfs filesystem >>exported by our zOS 1.4 system but I cannot get the configuration >>correct for zOS. I have tried diligently to follow the configuration >>process found in the "z/OS V1R2. Network File Systems Customization >>and Operations" manual (pub no. >>SC26-7417-02) but without any luck. >> >>I believe I have NFS installed correctly (including support for >>UNICODE) but I can't seem to get the EXPORT process to make a >>filesystem available. Can someone point me in the right direction? >> >>Thanks, >> >>Doug >> >>-- >>For LINUX-390 subscribe / signoff / archive access instructions, send >>email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or >>visit http://www.marist.edu/htbin/wlvindex?LINUX-390 >> >>-- >>For LINUX-390 subscribe / signoff / archive access instructions, send >>email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or >>visit http://www.marist.edu/htbin/wlvindex?LINUX-390 >> >>-- >>For LINUX-390 subscribe / signoff / archive access instructions, send >>email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or >>visit http://www.marist.edu/htbin/wlvindex?LINUX-390 >> >> > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the
Re: NFS question
That's a good manual. In the beginning of chapter 5, it says to start portmap. What does the command: rpcinfo -p mvs_system show, where mvs_system is your mvs host name? [EMAIL PROTECTED] wrote: If it is on by default, but I did not start PORTMAP. I just configured NFS based on the "z/OS Network File System Customization and Operation" manual. Is there a better manual to reference the installation of NFS? Also, can someone point me to where I can see syslogd? I don't know if there is any information there but I can't say I have ever looked at it. -Original Message- From: Michael Morgan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 10:10 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question The message indicating that port 2049 was not registered is an error. Do you have the PORTMAP address space started? ..thanks [EMAIL PROTECTED] wrote: When I start mvsnfs, there are no filesystems exported to be mounted I copied the following text from my system log file, but I can't see any error messages detailing what problem I am having. GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - VERSION 2 - FAILED. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 8:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question When I did it years ago, it seemed pretty straightforward. I wouldn't think it would have gotten more complicated with z/OS, but I could be wrong. What exactly are the symptoms you're seeing? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 09, 2005 6:06 PM To: LINUX-390@VM.MARIST.EDU Subject: NFS question I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the "z/OS V1R2. Network File Systems Customization and Operations" manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: NFS question
> GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER > (HDZ11TS) STARTED. > GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - > VERSION 2 - > FAILED. Your NFS server is not registering to handle the NFS RPCs. Did you modify TCPIP.ETC.RPC to include the entries for the NFS RPCs as shown on page 30 of SC26-7417? There's a whole set of steps in the NFS Customization and Operation manual starting at page 23 or so that have to get done before the NFS server will work. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: NFS question
If it is on by default, but I did not start PORTMAP. I just configured NFS based on the "z/OS Network File System Customization and Operation" manual. Is there a better manual to reference the installation of NFS? Also, can someone point me to where I can see syslogd? I don't know if there is any information there but I can't say I have ever looked at it. -Original Message- From: Michael Morgan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 10:10 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question The message indicating that port 2049 was not registered is an error. Do you have the PORTMAP address space started? ..thanks [EMAIL PROTECTED] wrote: >When I start mvsnfs, there are no filesystems exported to be mounted > >I copied the following text from my system log file, but I can't see >any error messages detailing what problem I am having. > >GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) >STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - >VERSION 2 - FAILED. > >-Original Message- >From: Post, Mark K [mailto:[EMAIL PROTECTED] >Sent: Tuesday, May 10, 2005 8:02 AM >To: LINUX-390@VM.MARIST.EDU >Subject: Re: NFS question > > >When I did it years ago, it seemed pretty straightforward. I wouldn't >think it would have gotten more complicated with z/OS, but I could be >wrong. > >What exactly are the symptoms you're seeing? > > >Mark Post > >-Original Message- >From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of >[EMAIL PROTECTED] >Sent: Monday, May 09, 2005 6:06 PM >To: LINUX-390@VM.MARIST.EDU >Subject: NFS question > > >I want to setup under Linux the ability to mount an hfs filesystem >exported by our zOS 1.4 system but I cannot get the configuration >correct for zOS. I have tried diligently to follow the configuration >process found in the "z/OS V1R2. Network File Systems Customization and >Operations" manual (pub no. >SC26-7417-02) but without any luck. > >I believe I have NFS installed correctly (including support for >UNICODE) but I can't seem to get the EXPORT process to make a >filesystem available. Can someone point me in the right direction? > >Thanks, > >Doug > >-- >For LINUX-390 subscribe / signoff / archive access instructions, send >email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or >visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > >-- >For LINUX-390 subscribe / signoff / archive access instructions, send >email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or >visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > >-- >For LINUX-390 subscribe / signoff / archive access instructions, send >email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or >visit http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: NFS question
The message indicating that port 2049 was not registered is an error. Do you have the PORTMAP address space started? ..thanks [EMAIL PROTECTED] wrote: When I start mvsnfs, there are no filesystems exported to be mounted I copied the following text from my system log file, but I can't see any error messages detailing what problem I am having. GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - VERSION 2 - FAILED. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 8:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question When I did it years ago, it seemed pretty straightforward. I wouldn't think it would have gotten more complicated with z/OS, but I could be wrong. What exactly are the symptoms you're seeing? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 09, 2005 6:06 PM To: LINUX-390@VM.MARIST.EDU Subject: NFS question I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the "z/OS V1R2. Network File Systems Customization and Operations" manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: NFS question
Anything in your syslogd logs on z/OS? [EMAIL PROTECTED] Sent by: Linux on 390 Port To <[EMAIL PROTECTED] LINUX-390@VM.MARIST.EDU IST.EDU> cc Subject 05/10/2005 11:27 Re: NFS question AM Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> When I start mvsnfs, there are no filesystems exported to be mounted I copied the following text from my system log file, but I can't see any error messages detailing what problem I am having. GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - VERSION 2 - FAILED. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 8:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question When I did it years ago, it seemed pretty straightforward. I wouldn't think it would have gotten more complicated with z/OS, but I could be wrong. What exactly are the symptoms you're seeing? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 09, 2005 6:06 PM To: LINUX-390@VM.MARIST.EDU Subject: NFS question I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the "z/OS V1R2. Network File Systems Customization and Operations" manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: NFS question
When I start mvsnfs, there are no filesystems exported to be mounted I copied the following text from my system log file, but I can't see any error messages detailing what problem I am having. GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - VERSION 2 - FAILED. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 8:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question When I did it years ago, it seemed pretty straightforward. I wouldn't think it would have gotten more complicated with z/OS, but I could be wrong. What exactly are the symptoms you're seeing? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 09, 2005 6:06 PM To: LINUX-390@VM.MARIST.EDU Subject: NFS question I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the "z/OS V1R2. Network File Systems Customization and Operations" manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: NFS question
When I did it years ago, it seemed pretty straightforward. I wouldn't think it would have gotten more complicated with z/OS, but I could be wrong. What exactly are the symptoms you're seeing? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 09, 2005 6:06 PM To: LINUX-390@VM.MARIST.EDU Subject: NFS question I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the "z/OS V1R2. Network File Systems Customization and Operations" manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
NFS question
I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the "z/OS V1R2. Network File Systems Customization and Operations" manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: MVS NFS question (almost there)
Mike ... It sounds like you NOW need to update your Apache config. Apache is pretty well locked-down by default. (good!) I re-build Apache often, and every time I have to go in and ALLOW access to certain directories. So ... even though wwwrun has Unix/POSIX permission, Apache won't touch it (and you get a 403) if the path is not configured for it in httpd.conf. Look in /etc/httpd for this config file (httpd.conf). -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: MVS NFS question
We found out what the 403 forbidden problem was after fixing the uid problem. Directory listing was not allowed so we couldnt view http://localhost/mymount we had to instead view http://localhost/mymount/MYPDSMEM We added INDEX to the DirectoryIndex line after index.html that way we can have an INDEX member in MYPDS It is sort of strange that we can get a directory index of a local unix subdirectory but not of the nfs mounted directory. Thanks Mike - Original Message - From: "Joachim Schmidt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 03, 2004 6:50 AM Subject: Re: MVS NFS question > hallo, > > ...as far as I remember passes mvslogin only the current UID/GID if > you have specified "security(saf)" or "secuity(safexp)". > Additionally you will have to define an user in MVS with same UID/GID > as your wwwrun-user and ensure that this user has access > to your MVS-PDS (correct the RACF-Profile if neccessary) . > > regards, > Joachim Schmidt > > > > > Mike Caughran wrote: > > >We have successfully mounted an MVS PDS using OS390 2.10 NFS on one of our > >linux guest os machines > >running SLES8. > > > >We mounted it under /srv/www/htdocs/mymount > > > >When we use apache to view files under /srv/www/htdocs/mymount we get an > >error saying > >"You don't have permission to access /mymount/ on this server." > > > >If we "su - wwwrun", we can then cd to /srv/www/htdocs but we cant > >cd from there into mymount either so it seems to be a problem with the > >wwwrun > >user in accessing mymount. > > > >We have experimented with combinations of "FollowSymlinks" in the httpd.conf > >We have experimented with the "-a" and "-g" account and group parms in the > >mvslogin command > >with no joy. > > > >Does anyone have any hints? > >This seems to be a basic thing. Making an mvs pds available on the web > >through apache. > > > > > >Thanks in advance, > > > >Mike > > > >PS the apache server is doing basic auth via ldap > > > >-- > >For LINUX-390 subscribe / signoff / archive access instructions, > >send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > >http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > > > > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: MVS NFS question (almost there)
That almost did it for me but I still am still getting 403 Forbidden from the SLES8 apache server. Here is what I did: Create a tso user with the same uid and group as wwwrun As the wwwrun user: mvslogin mvshost tsouser As root mount -t nfs TSOUSER.MYPDS,text /srv/www/htdocs/mountpoint After doing the above: If I try to cd to /srv/www/htdocs/mountpoint as root I get Permission denied If I try to cd to /srv/www/htdocs/mountpoint as wwwrun I am able to view files there with no problem If I try to access http://linuxbox/mountpoint/ I get 403 forbidden If I try as wwwrun using curl http://localhost/mountpoint/ I also get 403 forbidden So it looks like it works but for some reason the apache server isnt authorized to view the mount although the user under which the web server runs is allowed... Thanks Again Mike - Original Message - From: "Joachim Schmidt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 03, 2004 6:50 AM Subject: Re: MVS NFS question > hallo, > > ...as far as I remember passes mvslogin only the current UID/GID if > you have specified "security(saf)" or "secuity(safexp)". > Additionally you will have to define an user in MVS with same UID/GID > as your wwwrun-user and ensure that this user has access > to your MVS-PDS (correct the RACF-Profile if neccessary) . > > regards, > Joachim Schmidt > > > > > Mike Caughran wrote: > > >We have successfully mounted an MVS PDS using OS390 2.10 NFS on one of our > >linux guest os machines > >running SLES8. > > > >We mounted it under /srv/www/htdocs/mymount > > > >When we use apache to view files under /srv/www/htdocs/mymount we get an > >error saying > >"You don't have permission to access /mymount/ on this server." > > > >If we "su - wwwrun", we can then cd to /srv/www/htdocs but we cant > >cd from there into mymount either so it seems to be a problem with the > >wwwrun > >user in accessing mymount. > > > >We have experimented with combinations of "FollowSymlinks" in the httpd.conf > >We have experimented with the "-a" and "-g" account and group parms in the > >mvslogin command > >with no joy. > > > >Does anyone have any hints? > >This seems to be a basic thing. Making an mvs pds available on the web > >through apache. > > > > > >Thanks in advance, > > > >Mike > > > >PS the apache server is doing basic auth via ldap > > > >-- > >For LINUX-390 subscribe / signoff / archive access instructions, > >send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > >http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > > > > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: MVS NFS question
hallo, ...as far as I remember passes mvslogin only the current UID/GID if you have specified "security(saf)" or "secuity(safexp)". Additionally you will have to define an user in MVS with same UID/GID as your wwwrun-user and ensure that this user has access to your MVS-PDS (correct the RACF-Profile if neccessary) . regards, Joachim Schmidt Mike Caughran wrote: We have successfully mounted an MVS PDS using OS390 2.10 NFS on one of our linux guest os machines running SLES8. We mounted it under /srv/www/htdocs/mymount When we use apache to view files under /srv/www/htdocs/mymount we get an error saying "You don't have permission to access /mymount/ on this server." If we "su - wwwrun", we can then cd to /srv/www/htdocs but we cant cd from there into mymount either so it seems to be a problem with the wwwrun user in accessing mymount. We have experimented with combinations of "FollowSymlinks" in the httpd.conf We have experimented with the "-a" and "-g" account and group parms in the mvslogin command with no joy. Does anyone have any hints? This seems to be a basic thing. Making an mvs pds available on the web through apache. Thanks in advance, Mike PS the apache server is doing basic auth via ldap -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: MVS NFS question
Have you specified correct authentication options in the exportfs file on MVS ? Are the UID/GID on both systems matching ? Regards, Srinivas. Mike Caughran <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 06/03/04 04:21 AM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: MVS NFS question Yes we did, and we could access mymount as root but not as the wwwrun user. - Original Message - From: "Post, Mark K" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 02, 2004 2:21 PM Subject: Re: MVS NFS question > Did you use the "mvslogin" command to get authenticated by your MVS system? > > Mark Post > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mike > Caughran > Sent: Wednesday, June 02, 2004 6:16 PM > To: [EMAIL PROTECTED] > Subject: MVS NFS question > > > We have successfully mounted an MVS PDS using OS390 2.10 NFS on one of our > linux guest os machines running SLES8. > > We mounted it under /srv/www/htdocs/mymount > > When we use apache to view files under /srv/www/htdocs/mymount we get an > error saying "You don't have permission to access /mymount/ on this server." > > If we "su - wwwrun", we can then cd to /srv/www/htdocs but we cant cd from > there into mymount either so it seems to be a problem with the wwwrun user > in accessing mymount. > > We have experimented with combinations of "FollowSymlinks" in the httpd.conf > We have experimented with the "-a" and "-g" account and group parms in the > mvslogin command with no joy. > > Does anyone have any hints? > This seems to be a basic thing. Making an mvs pds available on the web > through apache. > > > Thanks in advance, > > Mike > > PS the apache server is doing basic auth via ldap > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send email > to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ForwardSourceID:NT7ABE DISCLAIMER: The information contained in this message is intended only and solely for the addressed individual or entity indicated in this message and for the exclusive use of the said addressed individual or entity indicated in this message (or responsible for delivery of the message to such person) and may contain legally privileged and confidential information belonging to Tata Consultancy Services. It must not be printed, read, copied, disclosed, forwarded, distributed or used (in whatsoever manner) by any person other than the addressee. Unauthorized use, disclosure or copying is strictly prohibited and may constitute unlawful act and can possibly attract legal action, civil and/or criminal. The contents of this message need not necessarily reflect or endorse the views of Tata Consultancy Services on any subject matter. Any action taken or omitted to be taken based on this message is entirely at your risk and neither the originator of this message nor Tata Consultancy Services takes any responsibility or liability towards the same. Opinions, conclusions and any other information contained in this message that do not relate to the official business of Tata Consultancy Services shall be understood as neither given nor endorsed by Tata Consultancy Services or any affiliate of Tata Consultancy Services. If you have received this message in error, you should destroy this message and may please notify the sender by e-mail. Thank you.
Re: MVS NFS question
Yes we did, and we could access mymount as root but not as the wwwrun user. - Original Message - From: "Post, Mark K" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 02, 2004 2:21 PM Subject: Re: MVS NFS question > Did you use the "mvslogin" command to get authenticated by your MVS system? > > Mark Post > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mike > Caughran > Sent: Wednesday, June 02, 2004 6:16 PM > To: [EMAIL PROTECTED] > Subject: MVS NFS question > > > We have successfully mounted an MVS PDS using OS390 2.10 NFS on one of our > linux guest os machines running SLES8. > > We mounted it under /srv/www/htdocs/mymount > > When we use apache to view files under /srv/www/htdocs/mymount we get an > error saying "You don't have permission to access /mymount/ on this server." > > If we "su - wwwrun", we can then cd to /srv/www/htdocs but we cant cd from > there into mymount either so it seems to be a problem with the wwwrun user > in accessing mymount. > > We have experimented with combinations of "FollowSymlinks" in the httpd.conf > We have experimented with the "-a" and "-g" account and group parms in the > mvslogin command with no joy. > > Does anyone have any hints? > This seems to be a basic thing. Making an mvs pds available on the web > through apache. > > > Thanks in advance, > > Mike > > PS the apache server is doing basic auth via ldap > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send email > to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: MVS NFS question
we used the mvslogin command to get authentication for out tso account (mytso). we can look at the sub directory and the files as root but not as wwwrun which is what apache runs as Post, Mark K wrote: Did you use the "mvslogin" command to get authenticated by your MVS system? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mike Caughran Sent: Wednesday, June 02, 2004 6:16 PM To: [EMAIL PROTECTED] Subject: MVS NFS question We have successfully mounted an MVS PDS using OS390 2.10 NFS on one of our linux guest os machines running SLES8. We mounted it under /srv/www/htdocs/mymount When we use apache to view files under /srv/www/htdocs/mymount we get an error saying "You don't have permission to access /mymount/ on this server." If we "su - wwwrun", we can then cd to /srv/www/htdocs but we cant cd from there into mymount either so it seems to be a problem with the wwwrun user in accessing mymount. We have experimented with combinations of "FollowSymlinks" in the httpd.conf We have experimented with the "-a" and "-g" account and group parms in the mvslogin command with no joy. Does anyone have any hints? This seems to be a basic thing. Making an mvs pds available on the web through apache. Thanks in advance, Mike PS the apache server is doing basic auth via ldap -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: MVS NFS question
Did you use the "mvslogin" command to get authenticated by your MVS system? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mike Caughran Sent: Wednesday, June 02, 2004 6:16 PM To: [EMAIL PROTECTED] Subject: MVS NFS question We have successfully mounted an MVS PDS using OS390 2.10 NFS on one of our linux guest os machines running SLES8. We mounted it under /srv/www/htdocs/mymount When we use apache to view files under /srv/www/htdocs/mymount we get an error saying "You don't have permission to access /mymount/ on this server." If we "su - wwwrun", we can then cd to /srv/www/htdocs but we cant cd from there into mymount either so it seems to be a problem with the wwwrun user in accessing mymount. We have experimented with combinations of "FollowSymlinks" in the httpd.conf We have experimented with the "-a" and "-g" account and group parms in the mvslogin command with no joy. Does anyone have any hints? This seems to be a basic thing. Making an mvs pds available on the web through apache. Thanks in advance, Mike PS the apache server is doing basic auth via ldap -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
MVS NFS question
We have successfully mounted an MVS PDS using OS390 2.10 NFS on one of our linux guest os machines running SLES8. We mounted it under /srv/www/htdocs/mymount When we use apache to view files under /srv/www/htdocs/mymount we get an error saying "You don't have permission to access /mymount/ on this server." If we "su - wwwrun", we can then cd to /srv/www/htdocs but we cant cd from there into mymount either so it seems to be a problem with the wwwrun user in accessing mymount. We have experimented with combinations of "FollowSymlinks" in the httpd.conf We have experimented with the "-a" and "-g" account and group parms in the mvslogin command with no joy. Does anyone have any hints? This seems to be a basic thing. Making an mvs pds available on the web through apache. Thanks in advance, Mike PS the apache server is doing basic auth via ldap -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
