Sponsored Content
Operating Systems AIX dedicated cpu for a user account Post 302327666 by shockneck on Monday 22nd of June 2009 09:38:39 AM
Old 06-22-2009
If you want to make sure that only dedicated CPU resources on a multiprocessor server is being used by some user/department/group I'd use the AIX Workload Manager.
If you want to bind a user's process to a dedicated processor on a multiprocessor server you need to know that you cannot exactly do that. However what you can do is bind the kernel threads of a process to a certain processor. The bindprocessor command is then what you are looking for.
Code:
 # bindprocessor <process-id> <processor#>

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

creatin user account

hi all, i m tryin to create a new account on the unix work station. do i use 'useradd' command? can u guyz advice on the usage of 'useradd' command as it can comes with 'useradd -D' or 'useradd -e' thanks :confused: (1 Reply)
Discussion started by: damian
1 Replies

2. UNIX for Dummies Questions & Answers

show all user account

I have a question about show all create user account. What commend do that thank`s for your help :) (6 Replies)
Discussion started by: Deux
6 Replies

3. Post Here to Contact Site Administrators and Moderators

user account

hi how to disable the useraccount in aix (should not remove). (1 Reply)
Discussion started by: chomca
1 Replies

4. UNIX for Dummies Questions & Answers

Difference between : Locked User Account & Disabled User Accounts in Linux ?

Thanks AVKlinux (3 Replies)
Discussion started by: avklinux
3 Replies

5. Shell Programming and Scripting

How to suspend a user account?

Hi, guys. I have two questions: I need to write a script, which can show all the non-suspended users on system, and suspend the selected user account. There are two things I am not sure: 1. How can I suspend user's account? What I think is: add a string to the encrypted password in shadow... (2 Replies)
Discussion started by: daikeyang
2 Replies

6. Solaris

Doubt on non global zone dedicated-cpu usage ??

Hi All, While creating zone we will mention min and max cpu cores, If the non global zone uses only minimum cores at particular time What the other cores will do? Will it shared to global zone? If we do prstat in non global zone is it show only the allocated cpu cores for that zone or it... (0 Replies)
Discussion started by: vijaysachin
0 Replies

7. Solaris

In Solaris Zones Dedicated-Cpu Performance?

Hi All, While creating zone we will mention min and max cpu cores, like add dedicated-cpu set ncpus=NUM_CPUS_MIN-NUM_CPUS_MAX end Ques1: Suppose thing that non global zone uses only minimum cores at particular time What the other cores will do, Will it shared to global zone? Ques:2... (1 Reply)
Discussion started by: vijaysachin
1 Replies

8. Solaris

Help me create new user account

I want create user. That user should be login to any server without asking password. How? tell me in detail. :wall: (3 Replies)
Discussion started by: Navkreddy
3 Replies

9. AIX

user account priviledges

Hi Admins, As per my knowledge there are two types of user accounts in unix. root and normal users. If there are any user types for which we can give some priviledges..? Actually i want to restrict root access and create new accounts for admins with some of the priviledges. Please let me... (6 Replies)
Discussion started by: newsol
6 Replies

10. HP-UX

User account

I need to check actual date a user was disabled on my HP-UX server. Audit is claiming the user account was active during the last audit exercise. (7 Replies)
Discussion started by: cyriac_N
7 Replies
SA(8)							    BSD System Manager's Manual 						     SA(8)

NAME
sa -- print system accounting statistics SYNOPSIS
sa [-abcdDfijkKlmnqrstu] [-P file] [-U file] [-v cutoff] [file ...] DESCRIPTION
The sa utility reports on, cleans up, and generally maintains system accounting files. The sa utility is able to condense the information in /var/account/acct into the summary files /var/account/savacct and /var/account/usracct, which contain system statistics according to command name and login id, respectively. This condensation is desirable because on a large sys- tem, /var/account/acct can grow by hundreds of blocks per day. The summary files are normally read before the accounting file, so that reports include all available information. If file names are supplied, they are read instead of /var/account/acct. After each file is read, if the summary files are being updated, an updated summary will be saved to disk. Only one report is printed, after the last file is processed. The labels used in the output indicate the following, except where otherwise specified by individual options: avio Average number of I/O operations per execution cp Sum of user and system time, in minutes cpu Same as cp k CPU-time averaged core usage, in 1k units k*sec CPU storage integral, in 1k-core seconds re Real time, in minutes s System time, in minutes tio Total number of I/O operations u User time, in minutes The options to sa are: -a List all command names, including those containing unprintable characters and those used only once. By default, sa places all names containing unprintable characters and those used only once under the name ``***other''. -b If printing command statistics, sort output by the sum of user and system time divided by number of calls. -c In addition to the number of calls and the user, system and real times for each command, print their percentage of the total over all commands. -d If printing command statistics, sort by the average number of disk I/O operations. If printing user statistics, print the average number of disk I/O operations per user. -D If printing command statistics, sort and print by the total number of disk I/O operations. -f Force no interactive threshold comparison with the -v option. -i Do not read in the summary files. -j Instead of the total minutes per category, give seconds per call. -k If printing command statistics, sort by the cpu-time average memory usage. If printing user statistics, print the cpu-time average memory usage. -K If printing command statistics, print and sort by the cpu-storage integral. -l Separate system and user time; normally they are combined. -m Print per-user statistics rather than per-command statistics. -n Sort by number of calls. -P file Use the specified file for accessing the per-command accounting summary database, instead of the default /var/account/savacct. -q Create no output other than error messages. -r Reverse order of sort. -s Truncate the accounting files when done and merge their data into the summary files. -t For each command, report the ratio of real time to the sum of user and system cpu times. If the cpu time is too small to report, ``*ignore*'' appears in this field. -U file Use the specified file for accessing the per-user accounting summary database, instead of the default /var/account/usracct. -u Superseding all other flags, for each entry in the accounting file, print the user ID, total seconds of cpu usage, total memory usage, number of I/O operations performed, and command name. -v cutoff For each command used cutoff times or fewer, print the command name and await a reply from the terminal. If the reply begins with ``y'', add the command to the category ``**junk**''. This flag is used to strip garbage from the report. By default, per-command statistics will be printed. The number of calls, the total elapsed time in minutes, total cpu and user time in min- utes, average number of I/O operations, and CPU-time averaged core usage will be printed. If the -m option is specified, per-user statistics will be printed, including the user name, the number of commands invoked, total cpu time used (in minutes), total number of I/O operations, and CPU storage integral for each user. If the -u option is specified, the uid, user and system time (in seconds), CPU storage integral, I/O usage, and command name will be printed for each entry in the accounting data file. If the -u flag is specified, all flags other than -q are ignored. If the -m flag is specified, only the -b, -d, -i, -k, -q, and -s flags are honored. FILES
/var/account/acct raw accounting data file /var/account/savacct per-command accounting summary database /var/account/usracct per-user accounting summary database EXIT STATUS
The sa utility exits 0 on success, and >0 if an error occurs. SEE ALSO
lastcomm(1), acct(5), ac(8), accton(8) AUTHORS
Chris G. Demetriou <cgd@postgres.berkeley.edu> CAVEATS
While the behavior of the options in this version of sa was modeled after the original version, there are some intentional differences and undoubtedly some unintentional ones as well. In particular, the -q option has been added, and the -m option now understands more options than it used to. The formats of the summary files created by this version of sa are very different from the those used by the original version. This is not considered a problem, however, because the accounting record format has changed as well (since user ids are now 32 bits). BUGS
The number of options to this program is absurd, especially considering that there is not much logic behind their lettering. The field labels should be more consistent. The VM system does not record the CPU storage integral. BSD
May 18, 2007 BSD
All times are GMT -4. The time now is 10:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy