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@(protected) [mailto:oracle-l-bounce@(protected)] On Behalf Of Jared Still Sent: Wednesday, June 15, 2005 12:25 PM To: nigel.tufnel1@(protected) Cc: Oracle-L@(protected) 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@(protected)> 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 > -- > http://www.freelists.org/webpage/oracle-l >=20
--=20 Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist
