Sponsored Content
Full Discussion: Prize of being an Admin
The Lounge War Stories Prize of being an Admin Post 302596711 by Neo on Wednesday 8th of February 2012 05:27:40 AM
Old 02-08-2012
I agree with zxmaus and the old saying:

"No good deed goes unpunished."

When in a political (territorial) situation as described; just fix the problem and don't tell anyone you fixed it, since you are the main system admin with root privs.

"No good deed goes unpunished."

.. as they say....
This User Gave Thanks to Neo For This Post:
 

6 More Discussions You Might Find Interesting

1. Solaris

fresh admin

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 Admin

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

note for admin

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?

Windows Admin switching to *nix Admin

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

Prize of being an Admin - Part 2

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?

Regarding Admin life either as DBA or UNIX Linux admin

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
nice(2) 							System Calls Manual							   nice(2)

NAME
nice - change priority of a process SYNOPSIS
DESCRIPTION
adds the value of priority_change to the nice value of the calling process. A process's is a positive number for which a more positive value results in lower CPU priority. A maximum nice value of 39 and a minimum nice value of 0 are imposed by the system. Requests for values above or below these limits result in the nice value being set to the corresponding limit. If the calling process contains more than one thread or lightweight process (i.e., the process is multi-threaded) this function shall apply to all threads or lightweight processes in the calling process. Security Restrictions Some or all of the actions associated with this system call are subject to compartmental restrictions. See compartments(5) for more infor- mation about compartmentalization on systems that support that feature. Compartmental restrictions can be overridden if the process pos- sesses the privilege (COMMALLOWED). Processes owned by the superuser may not have this privilege. Processes owned by any user may have this privilege, depending on system configuration. Some or all of the actions associated with this system call require the (OWNER) and/or the (LIMIT) privileges. Processes owned by the superuser will have these privileges. Processes owned by other users may have privilege(s), depending on system configuration. See privi- leges(5) for more information about privileged access on systems that support fine-grained privileges. RETURN VALUE
Upon successful completion, returns the new nice value minus 20. Otherwise, a value of -1 is returned and is set to indicate the error. Note that assumes a user process priority value of 20. If a user having appropriate privileges has changed the user process priority value to something less than 20, certain values for priority_change can cause to return -1, which is indistinguishable from an error return. ERRORS
[EPERM] fails and does not change the nice value if priority_change is negative or greater than 40, and the effective user ID of the calling process is not a user having appropriate privileges. SEE ALSO
nice(1), renice(1M), exec(2), privileges(5). STANDARDS CONFORMANCE
nice(2)
All times are GMT -4. The time now is 05:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy