It is my understanding that the process limit is checked in more than one place: 1. when a new process is being created 2. in the setuid function It appears that, in the later case, MAXPROCUSER (from PARMLIB) is being checked but not PROCUSERMAX from the user profile. APAR OA18535, which relates to incorrect behaviour when PROCUSERMAX > MAXPROCUSER, seems to be a variation on this theme.
Bill On Fri, 20 Oct 2006 09:16:58 -0500, Big Iron <[EMAIL PROTECTED]> wrote: >I had not been trying this with a process limit specified in the user >profile. I haven't tried specifying a larger value in the user profile but >when I put a smaller value, I got different behaviour which would seem to be >a defect. Here is the limits display before the first FTP session logs on: >D OMVS,L,PID=83886237 >BPXO051I 09.28.30 DISPLAY OMVS 026 >OMVS 000D ACTIVE OMVS=(00) >USER JOBNAME ASID PID PPID STATE START CT_SECS >FTPD FTPD2 0060 83886237 39 1FI--- 09.28.15 .136 > LATCHWAITPID= 0 CMD=/usr/sbin/ftpdns 0 0 27 1 80 128 256 >PROCESS LIMITS: LIMMSG=NONE > CURRENT HIGHWATER PROCESS > USAGE USAGE LIMIT >MAXFILEPROC 6 9 2000 >MAXFILESIZE --- --- NOLIMIT >MAXPROCUSER 25 30 NOLIMIT > >Here it is again after an FTP logon (userid edited out): >D OMVS,L,PID=83886237 >BPXO051I 09.28.44 DISPLAY OMVS 029 >OMVS 000D ACTIVE OMVS=(00) >USER JOBNAME ASID PID PPID STATE START CT_SECS >nnnnnnn nnnnnnn 0060 83886237 39 1FI--- 09.28.15 .219 > LATCHWAITPID= 0 CMD=/usr/sbin/ftpdns 2135760616 >PROCESS LIMITS: LIMMSG=NONE > CURRENT HIGHWATER PROCESS > USAGE USAGE LIMIT >MAXFILEPROC 8 9 2000 >MAXFILESIZE --- --- NOLIMIT >MAXPROCUSER 1 1 3 > >Then, we keep starting FTP sessions until we get: >BPXO051I 09.31.08 DISPLAY OMVS 054 >OMVS 000D ACTIVE OMVS=(00) >USER JOBNAME ASID PID PPID STATE START CT_SECS >nnnnnnn nnnnnnn 0060 83886237 39 1FI--- 09.28.15 .220 > LATCHWAITPID= 0 CMD=/usr/sbin/ftpdns 2135760616 >PROCESS LIMITS: LIMMSG=NONE > CURRENT HIGHWATER PROCESS > USAGE USAGE LIMIT >MAXFILEPROC 8 9 2000 >MAXFILESIZE --- --- NOLIMIT >MAXPROCUSER 4 4 3 > >which seems wrong. When you reach the process limit, this does appear to >inhibit starting processes from the shell, so there is a difference there. >(I went through this again with a slightly larger limit in the user profile >because I hit some problems running /etc/profile for a telnet session with a >process limit of 3.) If there isn't a limit set at the user level, then it >takes longer to hit the maximum, but then creation of either FTP and telnet >sessions or new processes is inhibited when we hit the process limit. > >Bill > >On Thu, 19 Oct 2006 13:40:50 -0500, Big Iron <[EMAIL PROTECTED]> wrote: > >>The FTP server actually starts a new process running under the userid of the >>person logging on to FTP so that data accesses will happen using that user's >>identity. >> >>Bill >> >>On Thu, 19 Oct 2006 13:15:45 -0400, Tim Hare <[EMAIL PROTECTED]> wrote: >> >>>Correct me if I'm wrong, but maybe, since the process is created by the >>>FTP server, wouldn't the process in question be created by the user ID of >>>the FTP server? I haven't ready any FTP code, but I'm thinking it >>>creates the process, then maybe does something like 'su' to have it run >>>under the ID of the person logging in. >>> >>>IF (and it's a big if I guess) that is the case, then the maximum that >>>applies is the one set to the user ID of the FTP server and you probably >>>don't want to limit that one. >>> >>>Tim Hare >>>Senior Systems Programmer >>>Florida Department of Transportation >>>(850) 414-4209 >>> >> > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
