Re:Fired employee wipes out whole season of TV show
by callmevlad on Friday April 01, 2011 @02:29AM
(#2395197)
Did the sysadmin also forget to create a backup for the repo? I don't think it's a stretch to assume that the developers were somewhat negligent in working on a single repo that can disappear at any time.
Re:Fired employee wipes out whole season of TV show
by palehose on Friday April 01, 2011 @02:43AM
(#2395229)
There was no backup of the CVS repository. The production server saved us since we were able to treat it as the definitive backup. This was before Git and the concept that everyone had their own copy of the entire repository.
There is a sort of half intent by the developer. Yes, the developer had intended to delete the repository that was in his home directory, but he had no idea that it was actually a link to the master repository.
Re:Fired employee wipes out whole season of TV show
by yardie on Friday April 01, 2011 @04:36AM
(#2395485)
The developer had hard links or symbolic links? It must have been a hard link to do that type of damage. I find that really dangerous and that's why I never use them. Unless you are using an obscure version of UNIX, rm -rf should delete the delete and not the content of the folder it is linked to.
Re:Fired employee wipes out whole season of TV show
by philwelch on Friday April 01, 2011 @05:00AM
(#2395540)
A hardlink would be safer in this case. If there are two hardlinks to the same file and you rm one of the hardlinks, the other hardlink still works and the file itself isn't deleted.
A symlinked directory, though, being made victim of a recursive rm command, just might result in rm traversing through the directory and deleting everything inside of it.
Having intent to destroy something on purpose is a different matter though, and I'm not sure that there is a good argument for it.