Sponsored Content
Full Discussion: user administration
Operating Systems Solaris user administration Post 302283908 by Gibby13 on Wednesday 4th of February 2009 10:14:25 AM
Old 02-04-2009
should be -g test(primary group) -G test1 (secondary group)
 

8 More Discussions You Might Find Interesting

1. Solaris

remote user administration

Hello, I inhearited several solaris machines (read that about 30 of them) and have a need to be able to manage the user accounts remotely.... Currently the machines all have the same users but not exactly the same spelling (each machine was locally managed before and thus every single passwd/shadow... (2 Replies)
Discussion started by: wgriffin
2 Replies

2. UNIX for Dummies Questions & Answers

User Administration

I have an application that runs on Unix and the user administration is managed at a Unix level. The application has an application ID which is linked to the user ids which are created at Unix level. Can you please help if I can be able to track which user used the Application ID and what action was... (0 Replies)
Discussion started by: Kopano
0 Replies

3. UNIX for Dummies Questions & Answers

Tru64 User administration

Hey guys how do you check if an account is locked in tru64, and how do you unlock it? (1 Reply)
Discussion started by: sbn
1 Replies

4. Solaris

Solaris User Administration

Hi All..... How many maximum no of users can be created in solaris 10.0 Waiting for the reply ..... (2 Replies)
Discussion started by: sendhils13
2 Replies

5. Solaris

Solaris User Administration

unable to run smgroup / smadd command to create or modify the users and directories. (1 Reply)
Discussion started by: sendhils13
1 Replies

6. Solaris

Zone administration

hi frnds I created sparse root zone, in that zone when i try to change the passwd it is giving permission denied. what is the reason and how to chnage the root passwd in the zone. can u please explain the query. (4 Replies)
Discussion started by: sravan ega
4 Replies

7. Shell Programming and Scripting

User administration

Dear All, I need to restrict the users in our server. 1.History & history -c command working all groups & others.So i need to restrict history -c option for groups & others . 2.Any option available to view user activity with all Eg--->user1 Jul22 10:20:11 date 3.Any other Special... (7 Replies)
Discussion started by: kpoobathi
7 Replies

8. AIX

AIX user administration - queue management

Dear All Please how can I create a user which would be only able to manage queue printer like creating, release, hold etc a printer queue. He would for example be able to enter commands like : - lpstat -pprintqueue where printqueue is an existing queue on the server - enable printqueue... (0 Replies)
Discussion started by: sobnc
0 Replies
CGEXEC(1)							 libcgroup Manual							 CGEXEC(1)

NAME
cgexec - run the task in given control groups SYNOPSIS
cgexec [-h] [-g <controllers>:<path>] [--sticky] command [arguments] DESCRIPTION
The cgexec program executes the task command with arguments arguments in the given control groups. -g <controllers>:<path> defines the control groups in which the task will be run. controllers is a list of controllers and path is the relative path to control groups in the given controllers list. This flag can be used multiple times to define multiple pairs of lists of controllers and relative paths. Instead of the list of all mounted controllers, the wildcard b"*b" can be used. If this option is not used, cgexec will automatically place the task in the right cgroup based on /etc/cgrules.conf. If /etc/cgrules.conf configuration file is used, there can be used template names. Then the control group name contains a template in destination tag (see cgrules.conf (5)) and if the cgroup does not exist in execution time, it is created, based on /etc/cgcon- fig.conf specification. If the specifications are not present the group is created with the default kernel values. -h, --help Display this help and exit. --sticky If running the task command with this option, the daemon of service cgred (cgrulesengd process) does not change both the task of the command and the child tasks. Without this option, the daemon does not change the task of the command but it changes the child tasks to the right cgroup based on /etc/cgrules.conf automatically. EXAMPLES
cgexec -g *:test1 ls runs command ls in control group test1 in all mounted controllers. cgexec -g cpu,memory:test1 ls -l runs command ls -l in control group test1 in controllers cpu and memory. cgexec -g cpu,memory:test1 -g swap:test2 ls -l runs command ls -l in control group test1 in controllers cpu and memory and control group test2 in controller swap. ENVIRONMENT VARIABLES
CGROUP_LOGLEVEL controls verbosity of the tool. Allowed values are DEBUG, INFO, WARNING or ERROR. FILES
/etc/cgrules.conf default libcgroup configuration file SEE ALSO
cgrules.conf (5) Linux 2009-03-15 CGEXEC(1)
All times are GMT -4. The time now is 07:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy