Sponsored Content
Operating Systems Solaris Sun Management Center installation fails Post 302211387 by incredible on Thursday 3rd of July 2008 08:08:31 AM
Old 07-03-2008
Edit the /etc/project file before performing setup of the Sun MC server. The database user is commonly allocated resources from the default project in the /etc/project file. Edit the applicable line of the /etc/project file to contain the following values:

default:3:::Smilieroject.max-shm-memory=(priv,5368708912,deny)
 

6 More Discussions You Might Find Interesting

1. High Performance Computing

Solaris 10 and OpenSolaris : Web Based Management tools and Sun Cluster installation

Gurus, I have several questions : 1. Does Solaris 10/OpenSolaris has some kind of web based management tools ? Currently I am using WebMin. It worked fine, however I am very curious to use the tools provided by Sun Microsystem. Please advise for package name and how to activate.... (0 Replies)
Discussion started by: Zepiroth
0 Replies

2. Solaris

Sun xVM Ops Center 1.1

I have 180 Solaris 7, 8 and 9 servers to patch and am looking at using xVM Ops Center. Has anyone here had any experience with it? (1 Reply)
Discussion started by: mr_crosby
1 Replies

3. Solaris

Sun Management Center 4.0

I need to create a managed job to monitor disk space on /tmp for db servers. How do you create a task in SMC to accomplish this? (1 Reply)
Discussion started by: soupbone38
1 Replies

4. Solaris

Sun Ops Center

Hi, Can anyone share the link to download sun ops centre i have sun partner account, but i unable find the link Thanks RJS (3 Replies)
Discussion started by: rajasekg
3 Replies

5. Solaris

Sun Management Center Database

Hi, I have some question regarding the Sun Management Center. Appreciate it if someone can answer: Conceptual: - Does the agent store any data on its side, or the entire data is transported to the management server? - In order to graph a data property, history logging, for that data... (2 Replies)
Discussion started by: Mack1982
2 Replies

6. Infrastructure Monitoring

Agent Installation Issue on Ops Center

Hi guys . While installing the agent on an asset Solaris system: root@system: /var/tmp/OC $ /opt/SUNWxvmoc/bin/agentadm configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 agentadm: Version 12.1.2.2161 launched with args: configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 Validating... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies
projadd(1M)						  System Administration Commands					       projadd(1M)

NAME
projadd - administer a new project on the system SYNOPSIS
projadd [-n] [-f filename] [-p projid [-o]] [-c comment] [-U user [,user...] ] [-G group [,group...] ] [ [-K name [=value [,value...]...]]] project DESCRIPTION
projadd adds a new project entry to the /etc/project file. If the files backend is being used for the project database, the new project is available for use immediately upon the completion of the projadd command. OPTIONS
The following options are supported: -c comment Add a project comment. Comments are stored in the project's entry in the /etc/project file. Generally, comments contain a short description of the project and are used as the field for the project's full name. Specify comment as a text string. comment cannot contain a colon (:) or <NEWLINE>. -f filename Specify the project file to modify. If no filename is specified, the system project file, /etc/project, is modified. -G group[,group...] Specify a group list for the project. -K name[=value[,value...] Specify an attribute list for the project. Multiple -K options can be specified to set values on multiple keys, such as: -K key1=value1 -K "key2=(value2a),(value2b)" Resource control attributes use parentheses to specify values for a key. Because many user shells interpret parentheses as special characters, it is best to enclose an argument to -K that contains parentheses with double quotes, as shown above and in EXAMPLES, below. See resource_controls(5) for a description of the resource controls you can specify for a project. -n Syntax check. Check the format of the existing system project file and modifications only. The contents of the existing project file, such as user names, group names, and resources that are specified in the project attributes are not checked. -o This option allows the project ID specified by the -p option to be non-unique within the project file. -p projid Set the project ID of the new project. Specify projid as a non-negative decimal integer below UID_MAX as defined in limits.h. projid defaults to the next available unique number above the highest number currently assigned. For example, if projids 100, 105, and 200 are assigned, the next default projid is 201. projids between 0-99 are reserved by SunOS. -U user[,user...] Specify a user list for the project. OPERANDS
The following operands are supported: project The name of the project to create. The project operand is a string consisting of characters from the set of alphabetic characters, numeric characters, underline (_), and hyphen (-). The period ('.') is reserved for projects with special mean- ing to the operating system. The first character of the project name must be a letter. An error message is displayed if these restrictions are not met. EXAMPLES
Example 1: Adding a Project The following command creates the project salesaudit and sets the resource controls specified as arguments to the -K option. projadd -p 111 -G sales,finance -c "Auditing Project" -K "rcap.max-rss=10GB" -K "process.max-file-size=(priv,50MB,deny)" -K "task.max-lwps=(priv,100,deny)" salesaudit This command would produce the following entry in /etc/project: salesaudit:111:Auditing Project::sales,finance: process.max-file-size=(priv,52428800,deny); rcap.max-rss=10737418240;task.max-lwps=(priv,100,deny) Note that the preceding would appear as one line in /etc/project. Comparing the projadd command and resulting output in /etc/project, note the effect of the scaling factor in the resource cap (rcap.max- rss=10GB) and the resource control (process.max-file-size=(priv,50MB,deny)). Modifiers, such as B, KB, and MB, and scaling factors are specified in resource_controls(5). EXIT STATUS
The following exit values are returned: 0 Successful completion. 2 The command syntax was invalid. A usage message for projadd is displayed. 3 An invalid argument was provided to an option. 4 The projid given with the -p option is already in use. 5 The project files contain an error. See project(4). 6 The project to be added, group, user, or resource does not exist. 9 The project is already in use. 10 Cannot update the /etc/project file. FILES
/etc/project System project file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +------------------------------+----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +------------------------------+----------------------------+ |Availability | SUNWesu | +------------------------------+----------------------------+ |Interface Stability | See below. | +------------------------------+----------------------------+ Invocation is evolving. Human readable output is unstable. SEE ALSO
projects(1), groupadd(1M), groupdel(1M), groupmod(1M), grpck(1M), projdel(1M), projmod(1M), useradd(1M), userdel(1M), usermod(1M), project(4), attributes(5), resource_controls(5) NOTES
In case of an error, projadd prints an error message and exits with a non-zero status. projadd adds a project definition only on the local system. If a network name service such as NIS or LDAP is being used to supplement the local /etc/project file with additional entries, projadd cannot change information supplied by the network name service. SunOS 5.10 30 Sep 2004 projadd(1M)
All times are GMT -4. The time now is 02:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy