<...>
> From my perspective, the simplest solution would be to rename that
> directory to something else
My solution would be to take away the offending sysadmin's hallucinogenic
drugs.
If that's not an option, then try suggesting that the script also check
for a real core file, or that it should only unlink() files, not directories.
Braindead:
find / -name core -exec rm -rf {} \;
Merely stupid:
find / -name core -type f -exec sh -c 'file {} | grep "core file" > /dev/null && rm -f {}' \;
More sensible would be to only delete it after it's 2 or 3 days old, to make
sure that people aren't currently trying to use it to debug programs. Our lot
would go apeshit if I did something as stupid as this.
> similar problems are almost bound to occur elsewhere for precicely
> the same reason
Nah, most people would just sack the idiot who did it, surely?
This has to be in academia, right? It sounds like just the kind of thing a
certain University Computing Service (which shall remain nameless) would do,
without either thinking about how much it'll f*** up the users, or caring after
it's pointed out.
---- ---- ----
David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/