02-08-2012
Difficult situation admin_xor . You dealt with the situation well on the back of an emergency ... but did you have the authority to make the change?
In a formal environment you needed authority from the duty Change Control Manager to go ahead with an Emergency Change.
This could have backfired big time.
Take care.
(I've had a Director out of bed to authorise a minor change when the duty Change Control Manager did not respond).
Last edited by methyl; 02-08-2012 at 07:14 PM..
Reason: stupid typo!
This User Gave Thanks to methyl For This Post:
6 More Discussions You Might Find Interesting
1. Solaris
hi everybody
i'm just recreuted as UNIX system admin...
please tell me from where do i have to begin...
best regards (8 Replies)
Discussion started by: hmaiida
8 Replies
2. Solaris
Tape: Need tape library help please. Need to configure a remote admin card in the L100. Anything helpful.....thxs (2 Replies)
Discussion started by: uwinix77
2 Replies
3. Post Here to Contact Site Administrators and Moderators
i left a message for admin in the wrong thread.. it is in the what is on your mind thread since i can't move it or delete it.. i thought I would mention that I meant it to be in this thread..
sorry about the mistake..
thanx for your patience moxxx68 (3 Replies)
Discussion started by: moxxx68
3 Replies
4. What is on Your Mind?
I'm currently a Windows admin and have wanted to jump ship to the *nix side for a while now. I've been studying both through an lpic level 1 manual as I have time (focusing on debian), and a solaris 10 cert book. The problem is I only have a handful of hours a week to study, and my current job... (3 Replies)
Discussion started by: bobwilson
3 Replies
5. War Stories
I was reading this thread of admin_xor Prize of being an Admin and thought will share this experience of mine which is kind of opposite to what he did - I didn't tell anybody what happened :D
We were porting one of the subsystem from Solaris to Linux. As part of that we developed many wrapper... (23 Replies)
Discussion started by: ahamed101
23 Replies
6. What is on Your Mind?
I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that.
Can we get "DAY" shifts in any one of the admin Job ?
Can't we have shift timings in any company ?
Eventhough the... (7 Replies)
Discussion started by: Jacktts
7 Replies
LEARN ABOUT OPENSOLARIS
nice
nice(2) System Calls nice(2)
NAME
nice - change priority of a process
SYNOPSIS
#include <unistd.h>
int nice(int incr);
DESCRIPTION
The nice() function allows a process to change its priority. The invoking process must be in a scheduling class that supports the nice().
The nice() function adds the value of incr to the nice value of the calling process. A process's nice value is a non-negative number for
which a greater positive value results in lower CPU priority.
A maximum nice value of (2 * NZERO) -1 and a minimum nice value of 0 are imposed by the system. NZERO is defined in <limits.h> with a
default value of 20. Requests for values above or below these limits result in the nice value being set to the corresponding limit. A nice
value of 40 is treated as 39.
Calling the nice() function has no effect on the priority of processes or threads with policy SCHED_FIFO or SCHED_RR.
Only a process with the {PRIV_PROC_PRIOCNTL} privilege can lower the nice value.
RETURN VALUES
Upon successful completion, nice() returns the new nice value minus NZERO. Otherwise, -1 is returned, the process's nice value is not
changed, and errno is set to indicate the error.
ERRORS
The nice() function will fail if:
EINVAL The nice() function is called by a process in a scheduling class other than time-sharing or fixed-priority.
EPERM The incr argument is negative or greater than 40 and the {PRIV_PROC_PRIOCNTL} privilege is not asserted in the effective set of
the calling process.
USAGE
The priocntl(2) function is a more general interface to scheduler functions.
Since -1 is a permissible return value in a successful situation, an application wishing to check for error situations should set errno to
0, then call nice(), and if it returns -1, check to see if errno is non-zero.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
|MT-Level |Async-Signal-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
nice(1), exec(2), priocntl(2), getpriority(3C), attributes(5), privileges(5), standards(5)
SunOS 5.11 1 Apr 2004 nice(2)