RE: OT moment of doubt

  • From: "Eric Buddelmeijer" <Eric.Buddelmeijer@xxxxxxxxxx>
  • To: <sorr@xxxxxxxxxxxx>
  • Date: Thu, 16 Jun 2005 16:02:40 +0200

Once every year we have a test rebuilding all our servers on a remote
location designed to have something left in case of a real disaster. We
always have a lively discussion who is allowed to execute the ultimate zap:
cd /
rm -fr *
Never seen a faster performing query.
Practising it, we hope we never do this in real life :-)
But you never get used to it, you always hesitate before hitting enter.

-----Oorspronkelijk bericht-----
Van: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
Namens Carel-Jan Engel
Verzonden: woensdag 15 juni 2005 22:41
Aan: sorr@xxxxxxxxxxxx
CC: oracle-l@xxxxxxxxxxxxx
Onderwerp: RE: OT moment of doubt

Jareds method is what I use most of the times.
When I'm really unsure, I run a small loop like (Apologies Jared, this still
isn't perl):
for file in *.dbf
   echo mv ${file} ${file}.GONE

When the results are OK, command history is my friend to repeat the whole
thing without the echo.

After a while, the *.GONE files can safely be removed. (Be sure the
essential program didn't have them opened al the time, unaware of the

Just my $0.02


If you think education is expensive, try ignorance. (Derek Bok) ===

On Wed, 2005-06-15 at 21:21, Orr, Steve wrote:

> Excellent comment Jared. A coupla years ago a sysadmin did something 
> similar and accidentally zapped lotsa directories. I ALWAYS do ls 
> first and even with that I have to take a deep breath before timidly 
> hitting <Enter>
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still
> Sent: Wednesday, June 15, 2005 12:25 PM
> To: nigel.tufnel1@xxxxxxxxx
> Cc: Oracle-L@xxxxxxxxxxxxx
> Subject: Re: OT moment of doubt
> Every time I do it.
> When using a command like that, I usually check=20 it with ls first, 
> then modify the command.
> eg.
> ls -l *.dbf
> If that gets the expected results, I will then call up the command 
> line history and replace the 'ls -l'=20 with 'rm -f'.
> This not only ensures the results are what I expect, but avoids fat 
> fingering that occur if the entire command is retyped:
> eg. rm -f * .dbf
> Notice the space between * and .dbf.
> Jared
> On 6/15/05, Joe <nigel.tufnel1@xxxxxxxxx> wrote:
> >=20
> > What would you call that moment in time after you do "rm *.dbf" on 
> >all  your database files, where you suddenly panic about whther 
> >you're on  the right server or not?
> >=20
> > This happens to me all the time, even after checking, even after 17  
> >yrs of DBA-ing. Kinda like that feeling you get when your chair 
> >starts  to tip over backwards but you catch yourself.
> >=20
> > :P
> >=20
> > Joe
> > --
> >
> >=20
> --=20
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
> --
> --



Other related posts: