Sponsored Content
Operating Systems AIX Maxuproc parameter and number of processes Post 303033297 by Don Cragun on Wednesday 3rd of April 2019 04:19:09 AM
Old 04-03-2019
Before your last post, I thought you were saying that one (non-root) user was having problems. Do you mean that all non-root users are having jobs killed by the system?

Does AIX have a fixed process table size? If so, what fixed process table size is currently configured and how many processes does ps -ef show running for all users?
 

10 More Discussions You Might Find Interesting

1. Solaris

How to find number of processes ?

Hi , I need to count all processes contains the pattren "FND" For Example: I was reteriving the details of all processes related to "FND" by this command $ ps -ef | grep FND but now I just wanna count them . Regards Adel (2 Replies)
Discussion started by: ArabOracle.com
2 Replies

2. UNIX for Dummies Questions & Answers

checking if parameter passed is a number

I have written a function that fills an array and another function where if a parameter is supplied it will jump to that part of the array and cat it to the screen. I need to put in some checks to make sure the parameter supplied is firstly a number and then not a number great than the length of... (2 Replies)
Discussion started by: magnia
2 Replies

3. Programming

How to limit the number of child processes

I need a mechanism to fork child processes and all child processes should connect to a server.but the number of child processes should be limited(for ex:50) Here's my pseudo, but I cant figure out how to limit the child process number. Should I use a semaphore? or what? for(;;)... (3 Replies)
Discussion started by: xyzt
3 Replies

4. Shell Programming and Scripting

Dynamic number of parameter

Hi all Is there away to create a script with dynamic number of parameter.. like the kill command in UNIX kill -9 xxx xxx cheers (4 Replies)
Discussion started by: co0oly
4 Replies

5. Shell Programming and Scripting

How to Control Number of Processes Running

Hi Is there a way to count how many processes a script has started, count how many of these have finished, and make the script wait if their difference goes over a given threshold? I am using a script to repeatedly execute a code (~100x) which converts 2 data files into one .plt which is in... (4 Replies)
Discussion started by: drbones
4 Replies

6. Shell Programming and Scripting

Check parameter is number or string

Hey I'm new in linux, I'm looking for a code to check whether the parameter is a number or a string. I have already tried this code: eerste=$(echo $1 | grep "^*$">aux) if But it doesn't work.:confused: Thanks (2 Replies)
Discussion started by: Eclecticaa
2 Replies

7. AIX

Maximum number of processes kernel parameter

Hi, Is there a maximum number of processes kernel parameter in AIX. Solaris has max_nprocs, HP-UX has nproc, I can only find max user process (maxuproc) for AIX. Thanks, Wilson. (3 Replies)
Discussion started by: wilsonee
3 Replies

8. AIX

Maxuproc vs ulimit -u [processes(per user)]

Morning, Somebody can tell me in AIX 6.1 what is the different between the maxuproc (lsattr -El sys0 | grep max) and the for a user. Example: Oracle is limited by : #ulimit -u processes(per user) unlimited But lsattr -El sys0| grep maxuproc show me : maxuproc 16384 So... (1 Reply)
Discussion started by: bacup540
1 Replies

9. UNIX for Dummies Questions & Answers

Maxuproc and limit

// AIX 6.1 & Power 7 server I have maxuproc set to 16384. lsattr -El sys0 -a maxuproc maxuproc 16384 Maximum number of PROCESSES allowed per user True What is the maximum number of maxuproc we can go for? If I increase maxuproc to the higher number, what would be ramifications? I... (1 Reply)
Discussion started by: Daniel Gate
1 Replies

10. Red Hat

Increase maxuproc value

Hi Guys, I am running RHEL6 and now my processes reach maximum limit. How do I increase the maxuproc value? Can I increase the value without rebooting the server? Thanks in advance... Please Help!!! (5 Replies)
Discussion started by: Phuti
5 Replies
SYSTEMD-LOGIND.CO(5)                                            systemd-logind.conf                                           SYSTEMD-LOGIND.CO(5)

NAME
systemd-logind.conf - Login manager configuration file SYNOPSIS
systemd-logind.conf DESCRIPTION
This files configures various parameters of the systemd login manager. OPTIONS
All options are configured in the [Login] section: NAutoVTs= Takes a positive integer. How many virtual terminals to allocate by default and when switched to autospawn autovt services on (if they are otherwise unused). These services are instantiated from a template of autovt@.service with the virtual terminal TTY name, e.g. autovt@tty4.service. By default autovt@.service is linked to getty@.service, i.e. login prompts are started dynamically as the user switches to unused virtual terminals, and this parameter hence controls how many gettys are available on the virtual terminals. Defaults to 6. When set to 0, automatic spawning of autovt services is disabled. KillUserProcesses= Takes a boolean argument. Configures whether the processes of a user should be killed when she or he completely logs out (i.e. after her/his last session ended). Defaults to no. KillOnlyUsers=, KillExcludeUsers= These settings take space separated lists of user names that influence the effect of KillUserProcesses=. If not empty only processes of users listed in KillOnlyUsers will be killed when they log out entirely. Processes of users listed in KillExcludeUsers= are excluded from being killed. KillExcludeUsers= defaults to root and takes precedence over KillOnlyUsers= which defaults to the empty list. Controllers=, ResetControllers= These settings control the default control group hierarchies users logging are added to. When logging in users will get private control groups in all hierarchies listed in Controllers= and be reset to the root control group in all hierarchies listed in ResetControllers=. Controllers= defaults to the empty list, ResetControllers= defaults to cpu. Note that setting KillUserProcesses=1 will break tools like screen(1). Note that KillUserProcesses=1 is a weaker version of kill-session-processes=1 which may be configured per-service for pam_systemd(8). The latter kills processes of a session as soon as it ends, the former kills processes as soon as the last session of the user ends. SEE ALSO
systemd(1), systemd-loginctl(1), systemd.conf(5) AUTHOR
Lennart Poettering <lennart@poettering.net> Developer systemd 10/07/2013 SYSTEMD-LOGIND.CO(5)
All times are GMT -4. The time now is 08:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy