Dumb use of rm

[Zathros]

Ok, I did it, I'll admit it. A stupid stupid mistake. I had to clean out some files and directories under a software providers temp directory and when I did rm -R * as muself in that directory it would take out all the files due to permissions. So I su'd to root and did the cammand... only to realzie in horror after I typed it that I didnt change to the developers temp directory and was in root. I began pounding interupt key sequences and eventually got the command prompt back.

How can I tell what got deleted? /etc and other directories look ok.

 

[PHV]

How can I tell what got deleted?
Compare with backup.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[motoslide]

There are utitlies in "custom" to verify O/S files, but they won't help you with your 3rd-party apps, $HOME directories, or other such things.

You could perform a listing on a recent backup tape, and use that list to compare to what's left. That would be quite tedious.

I don't know what order the "rm -R" would remove files. If it runs in the same order as the directories were created, your "/etc" and "/stand" would be the first to go. If it runs in "alpha" order, then you'd have problems in /bin. Either way, it's one of those things you seldom do twice!

If your hope is to salvage the system, I'd do all you can before rebooting. You may have a system that will not boot.

 

[Zathros]

Thanks. 3rd party files are already showing up missing but my main data directory is ok.

I'll run the custom checks and contact lone-tar and see if I can do a restore whats missing from last nights master.

 

[Zathros]

PHE

http://WWWWWWWWWWWWWw!!!

Custom verify tools showed system is good, only a couple broken links.

Lonetar is now doing a non-destructive restore that will replace anything not on the disk.

Now the knot in my stomach is down from basketball size to golfball size.

Thanks for the help. Just responding so fast was a big plus!