On 3/28/2011 12:07, Dante Allegria wrote: > --- On Mon, 3/28/11, Damon Register <damon.w.regis...@lmco.com> wrote: > >> this at a company. Is that so? Do you have an >> aggressive IS department who might have decided they don't like Cygwin? > > No, turns out it was because someone committed this into the nightly build > scripts: > rm -rf $(DOES_NOT_EXIST)/* > > <sigh> Should cygwin's rm have some built-in safeguards for this? :)
Probably the only way to get this protection would be to remove the ability of the user running your build automation to delete the Cygwin installation in the first place. Otherwise, this could just as easily happen somewhere else such as a Perl script that doesn't even use rm. Depending on your situation, that may be easier said than done unfortunately. -Jeremy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
