|
|
Sponsored Content
The Lounge
What is on Your Mind?
Knowing the half will get you into trouble - describe your disasters
Post 302189333 by sparcguy on Friday 25th of April 2008 12:48:12 PM
04-25-2008
I only happened to be next to her when it went down, she just got married recently and maybe still on honeymoon mood and probably still dazed and day dreaming 
... and did something that should never have been done on a very critical production system. She was very young at that time and very inexperienced, it was a very good but painful lesson for her. She will remember it for the rest of her life I think.
I remember the aftermath was terrible, we had endless conference calls late into the night, meetings after meetings explaining over and over to angry people calling in from all over the globe at different time zones wanting to know what the heck was going on and they were screaming the blame at each other during the calls it was like being at fish market and we're right there in the middle of a shit storm and you will just get the sinking feeling that somebody's head is going to roll if you say the wrong thing.
I will not say how it all started or what the outcome was as you never know who visits unix.com these days.
Anyway the bottom line is this, if you are ever caught in such a situation whether it's your fault or not. In a heated situation where everybody is angry screaming and shouting, DONT EVER tell the truth immediately, delay it a day or two.
if you tell truth somebody's definitely going to get sacked on the spot maybe you, maybe your friend or both of you. Don't give in to pressure just delay it! delay it after a day or two by then the system would have already been restored, service resumed back to normal and the incident will be largely ignored by then due to other new pressing issues of the day starting to come in and there will be very much lesser angry people around.
Though I should tell you that this customer will probably never trust you again in the future and maybe you will even even lose his business when the time for contract renewal comes around so it's 50-50 choice and both are difficult to make.
I actually learned this from another incident that actually happened many years before this incident and the earlier incident was my own fault being young and inexperienced myself once before and a more experienced friend helped me out, we did the same thing and it worked so this counts as paying it forward.
So lesson learned: Never give root access to "just married" newbies(just kidding)
... and did something that should never have been done on a very critical production system. She was very young at that time and very inexperienced, it was a very good but painful lesson for her. She will remember it for the rest of her life I think. I remember the aftermath was terrible, we had endless conference calls late into the night, meetings after meetings explaining over and over to angry people calling in from all over the globe at different time zones wanting to know what the heck was going on and they were screaming the blame at each other during the calls it was like being at fish market and we're right there in the middle of a shit storm and you will just get the sinking feeling that somebody's head is going to roll if you say the wrong thing.
I will not say how it all started or what the outcome was as you never know who visits unix.com these days.
Anyway the bottom line is this, if you are ever caught in such a situation whether it's your fault or not. In a heated situation where everybody is angry screaming and shouting, DONT EVER tell the truth immediately, delay it a day or two.
if you tell truth somebody's definitely going to get sacked on the spot maybe you, maybe your friend or both of you. Don't give in to pressure just delay it! delay it after a day or two by then the system would have already been restored, service resumed back to normal and the incident will be largely ignored by then due to other new pressing issues of the day starting to come in and there will be very much lesser angry people around.
Though I should tell you that this customer will probably never trust you again in the future and maybe you will even even lose his business when the time for contract renewal comes around so it's 50-50 choice and both are difficult to make.
I actually learned this from another incident that actually happened many years before this incident and the earlier incident was my own fault being young and inexperienced myself once before and a more experienced friend helped me out, we did the same thing and it worked so this counts as paying it forward.
So lesson learned: Never give root access to "just married" newbies(just kidding)
|
|
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
the following unix command
ls | grep'?cw1' | wc -l
converting it to english is it going to be like
list the result of the search '?cw1' in number of lines
is that correct ? (4 Replies)
Discussion started by: props
4 Replies
2. UNIX for Dummies Questions & Answers
I am confused about what this line of code would do. I understand all the pieces but not the final outcome. Anyone that could help?
find / -type f -xdev -mtime 0 -size 100000 -exec ls -lht {} /; 2>/dev/null (4 Replies)
Discussion started by: NickNine
4 Replies
3. Shell Programming and Scripting
Some software, when you install it, prompts you for variables, such as the username for the software, or the password you are setting for the software's root account.
I would like to know if it is possible to do such a thing, and if yes, how?
basically, I would like my installer script to prompt... (3 Replies)
Discussion started by: Bakes
3 Replies
4. UNIX for Advanced & Expert Users
Hi all.
can you please tell me
(root) NOPASSWD: ALL
what this command means (1 Reply)
Discussion started by: mindtee_abhi
1 Replies
5. Solaris
What is openboot prompt
is this some kind of shell , and where is located :p (2 Replies)
Discussion started by: solaris_user
2 Replies
6. Solaris
Hi I have a requirement like we are creating a zone in which we are installing oracle and in the global zone we are installing our project related software..
Now my question is how to manage the solaris zone from any faults happen??
like it may be Memory,Network etc............
I want to know... (2 Replies)
Discussion started by: vijaysachin
2 Replies
7. Shell Programming and Scripting
Hi everyone I'm new here and I don't know some command of unix, please help by describe me how it work, I study unix command by myself and can't search exactly means so...Thanks :D
sqlplus -s /nolog @${SQLFILE} ${file_type} >> ${OUTPUT_FILE}
date "+%Y%m%d%H%M%S"
$/usr/bin/echo "INFO : $1"... (2 Replies)
Discussion started by: zound617
2 Replies
8. UNIX for Advanced & Expert Users
I never understood what exactly it is that preempts a process in a preemptive multitasking system. For example, round-robin, SRTF, or preemptive priority-based algorithms. I understand how the algorithm works, but what exactly triggers the preemption? I know in the case of round-robin... (4 Replies)
Discussion started by: Ultrix
4 Replies
LEARN ABOUT PHP
holidays
holidays(4) File Formats holidays(4) NAME
holidays - prime/nonprime table for the accounting system SYNOPSIS
/etc/acct/holidays DESCRIPTION
The /etc/acct/holidays file describes which hours are considered prime time and which days are holidays. Holidays and weekends are con- sidered non-prime time hours. /etc/acct/holidays is used by the accounting system. All lines beginning with an "*" are comments. The /etc/acct/holidays file consists of two sections. The first non-comment line defines the current year and the start time of prime and non-prime time hours, in the form: current_year prime_start non_prime_start The remaining non-comment lines define the holidays in the form: month/day company_holiday Of these two fields, only the month/day is actually used by the accounting system programs. The /etc/acct/holidays file must be updated each year. EXAMPLES
Example 1: Example of the /etc/acct/holidays file. The following is an example of the /etc/acct/holidays file: * Prime/Nonprime Table for the accounting system * * Curr Prime Non-Prime * Year Start Start * 1991 0830 1800 * * only the first column (month/day) is significant. * * month/day Company Holiday * 1/1 New Years Day 5/30 Memorial Day 7/4 Indep. Day 9/5 Labor Day 11/24 Thanksgiving Day 11/25 day after Thanksgiving 12/25 Christmas 12/26 day after Christmas SEE ALSO
acct(1M) SunOS 5.10 28 Mar 1991 holidays(4)