Sponsored Content
Full Discussion: Prize of being an Admin
The Lounge War Stories Prize of being an Admin Post 302596560 by admin_xor on Tuesday 7th of February 2012 06:51:27 PM
Old 02-07-2012
Prize of being an Admin

Was wondering if anyone has come across any situation where you do your best to help users and in return you get a nice escalation from top level management!

Here's my story:

One fine morning, I was sitting idle, doing next to nothing, I got an alert from helpdesk people about a problem with an application running on a high-priority AIX LPAR (sorry for not being specific as I am not allowed to disclose the details). This application is actually used heavily by the bio-tech research fellows. The application was crashing frequently. Upon checking in-depth, I found there's nothing wrong from the OS stand point. I also found the problem was caused by one rouge wrapper script. But as a server admin, I had nothing to do with that officially. In the mean time, I had to speak to the manager of the research team and had to try my best to make her understand where the actual problem was. I assured her that I would contact the responsible application admin team.

Followed by that, I tried contacting that application admin team (which is a different IT services vendor than my company). I did not get any solid reply from them nor any definite timeline when they would be able to look into the problem.

I ended my shift. Still no reply from the application team. I came home. Gave it a lot of thought whether I should modify the script by myself. I accessed the server from home, spent a sleepless night understanding how everything of that application was wired.

Next morning, I went to office, saw my E-mail inbox hoping that the app team might have responded. But no! So I went ahead, made the changes that I thought should have been done. restarted the application service. Monitored the application for a couple of hours and called up the manager of the research team. She was furious. I politely told what I had done so far and asked her to check if things were fine. And yes, things were fine. But that lady was quite upset about our service.

After 6 hours, I saw an E-mail from our top level Service Delivery Manager demanding an answer as to why it took so long for me to fix the issue. Upon checking I found the research team manager had sent a "beautiful" E-mail to the top level manager saying how worthless people in IT were.

After two days, my supervisor showed up after his vacation. After knowing my deed, all he had to ask was "Why the hell did you even think of taking such bold step? What if something wrong had happened?". Being one of the junior members in the team, I kept quiet. All I tried to do was to help the research folks out and let them continue their work as soon as possible. But I got the prize of doing that. Smilie
 

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
renice(1M)																renice(1M)

NAME
renice - alter priority of running processes SYNOPSIS
newoffset] id ... DESCRIPTION
The command alters the system nice value (used in the system scheduling priority) of one or more running processes specified by id .... The new system nice value is set to 20 + newoffset, and is limited to the range 0 to 39. However if the environment variable is set, the new system nice value is set to current nice value + newoffset. Processes with lower system nice values run at higher system priorities than processes with higher system nice values. The option of the command shows the current priority and nice value for processes. See also nice(1). To reduce the system nice value of a process, or to set it to a value less than 20 (with a negative newoffset), a user must have appropri- ate privileges. Otherwise, users cannot decrease the system nice value of a process and can only increase it within the range 20 to 39, to prevent overriding any current administrative restrictions. To alter the system nice value of another user's process, a user must have appropriate privileges. Otherwise, users can only affect pro- cesses that they own. Options recognizes the following options. If no or option is specified, the default is Interpret each id as a process group ID. All processes in each process group have their system nice value altered. Only users with appropriate privileges can use this option. Change the system nice value of each affected process to 20 + newoffset. If the environment variable is set, the system nice value of each affected process is changed to current nice value + newoffset. If newoffset is negative, the system nice value is set to 20 minus the absolute value of newoffset. If the environ- ment variable is set and the newoffset is negative, the system nice value is set to current nice value minus the absolute value of newoffset. Only users with appropriate privileges can reduce the system nice value or set it to less than 20. If this option is omitted, newoffset defaults to 10. Interpret each id as a process ID. This is the default. Note: id is a process ID as reported by the command, not a job number (e.g., as used by some shells. Interpret each id as a user name or user ID number. All processes owned by each specified user have their system nice values altered. Only users with appropriate privileges can use this option for user names and IDs other than their own. RETURN VALUES
returns a 0 when successful, and a non-zero value when unsuccessful. EXTERNAL INFLUENCES
Single-byte character code sets are supported. DIAGNOSTICS
reports the old and new newoffset values (system nice value - 20) of the affected processes if the operation requested completes success- fully. Otherwise, an error message is displayed to indicate the reason for failure. However, if the environment variable is set, no reporting is done unless the command fails. EXAMPLES
Use default values to decrease the priority of process The id type defaults to and newoffset defaults to setting the process to a system nice value of 30. Change the system nice value for all processes owned by user and user to 33 (newoffset=13). (Affecting other users processes requires appropriate privileges.) Change the system nice value of all processes in process group 20 to (Lowering the system nice value of a process group requires appropri- ate privileges.) WARNINGS
Users who do not have appropriate privileges cannot reduce the system nice values of their own processes, even if they increased them in the first place. FILES
Maps user names to user ID's SEE ALSO
nice(1), ps(1), getpriority(2), nice(2). STANDARDS CONFORMANCE
renice(1M)
All times are GMT -4. The time now is 03:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy