dieter@titan.nmt.edu (12/04/88)
The symptoms: We've been noticing that /lib/ccom on one of our 3/280s (titan) will start core dumping almost instantly upon start up. Doing a "diff" with the same file on our other 3/280 (jupiter) doesn't report any problems. Once it starts happening, the odds of getting a successful compile rapidly approach zero. If we rcp /lib/ccom from jupiter, everything works again. This seems to recur on about a 6 month cycle. /lib/ccom has only died on titan, never on jupiter. The questions: Does this sound like a familiar problem to anyone? If so, anyone have a fix? BTW, the inode number for /lib/ccom is 79. Ideas? Dieter Muller -- dieter%nmt@relay.cs.net dieter@jupiter.nmt.edu [[ I like the machine's name! :-) --wnl ]]
smb@research.att.com (12/14/88)
We've sometimes seen similar symptoms that we've attributed to a corrupted swap area copy of some file -- with us, it's usually grep. A reboot cures it.