Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!romp!auschs!awdprime!codesmith.austin.ibm.com!dcm From: dcm@codesmith.austin.ibm.com (Craig Miller) Newsgroups: comp.unix.aix Subject: Re: AIX problems Message-ID: <7513@awdprime.UUCP> Date: 13 May 91 15:28:44 GMT References: <9357.282caa94@jetson.uh.edu> Sender: news@awdprime.UUCP Organization: IBM AWD, Austin Lines: 42 In article <9357.282caa94@jetson.uh.edu> elee4fg@jetson.uh.edu writes: >From: seng Gan >Star Enterprise > >1) csh does not support suid. If your csh suid scripts file has this > #!/bin/csh > It won't work. > Your need to do this in ksh I believe this is not an AIXism but is a BSDism. The BSD4.3 csh source I have access to does not support suid either. This is documented, I believe. > /bin/csh ( without #!/bin/csh ) Are you sure this really works? Suid scripts have never worked without "#!". Your script may run, but it won't run suid. >6) Increase your process limit > your need to edit /usr/include/sys/limits.h > CHILD_MAX to increase your number of process allowed per user id > in ksh 40 is too small for root > chdev -l sys0 -A maxuproc has no effect in ksh (a) /usr/include/sys/limits.h has no effect on process limits (unless you're rebuilding your kernel). Are you rebuilding your kernel? (b) I wasn't aware that max number of procs per user was enforced for root. If it is, it shouldn't be (IMHO). (c) What does ksh have to do with process limits? Can you give a more specific example of why "chdev -l sys0..." has no effect in ksh (vs sh or csh). Craig -- Craig Miller Internet: dcm@aixwiz.austin.ibm.com IBM Austin Vnet: tkg007 at ausvmq AIXV3 Change Team (level3) IBM internal: dcm@littleguy.austin.ibm.com "I do not represent IBM or any other respectable company."