I recieved several replies to this and have seen others like it since mine.
We discovered a bad cron job that was supossed to remove cores and it was
removing files at random or maybe not so random but by I-nodes. Nobody with
root access will attest to editing the cron entry which worked fine for a long
time before going bad (It seems somebody deleted the -name option from the
find). We haven't disregarded the possibility of a hacker but more than likely
it was one of our own people who are afraid to fess up.
Thanks to all who repied
dabe@cs.UMD.EDU
fetrow@biostat.washington.edu
ian@ironbark.ucnv.edu.au
jared@osiris.ac.hmc.edu
jram@morgan.com
solomon!kevinc@qiclab.scn.rain.com
see@uebemc.siemens.de
anderson@neon.mitre.org
melissa@tintin.cc.columbia.edu
0085P%NAVPGS.BITNET@cmsa.Berkeley.EDU
strombrg@hydra.acs.uci.edu
wpmc!mother!cygan@uu5.psi.com
eckhard@ts.go.dlr.de
/------------------------------------------------------------------------\
|GARY A WHITE | |
|SYSTEM ADMINISTRATOR | "A day without laughter |
|1912TH COMPUTER SYSTEMS GROUP | is a day wasted" |
|LANGLEY AFB VA. 23665 | Graucho Marx |
|E-MAIL <whiteg@panther.acc1912.af.mil> | |
\------------------------------------------------------------------------/
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:34 CDT