Hi Howard, I deal more with debian based systems. For those there's a package called "debsums" (unfortunately I had to use not so long ago before I left Vanderbilt, after I could magically fix a fallen-apart RAID5 partition), which can find broken packages: http://raphaelhertzog.com/2011/02/21/debian-cleanup-tip-4-find-broken-packages-and-reinstall-them/
I'm 100% sure that rpm package management systems also have checksums and capabilities to do such, so there must be a way to find broken files. Then you can reinstall or force reinstall the affected packages. If such a software file system failure comes into the picture, an fsck is also a good idea. Then a debsums again after that :). Another thing. Please don't beat me up with a stick for this, but as a developer I'd try to get the callstack from the crashdump. Even for a non developer it might give a clue about the crash. However, you'd need a gdb (GNU debugger) for that, but since you mention that this is a production system, there's a good chance you may not have gdb there. Actually it is better if you don't have: because developer tools could be very handy for a hacker in case of a break-in. Csaba ________________________________________ From: [email protected] [[email protected]] On Behalf Of Howard White [[email protected]] Sent: Tuesday, September 18, 2012 7:25 AM To: [email protected] Subject: [nlug] Yet another plaint from your not so super SysAdmin Here's a burr in anyone's saddle -- when I arrived at this job, a2ps worked fine on the prime production system. It's a print routine for Pete's sake... A few weeks pass and now when I attempt to "a2ps -P printera some-file.txt" I get segmentation fault. What??? More importantly - what to do? Yum info tells me version 4.13b from Release 57.2.el5 (CentOS 5.7). Yum check-update a2ps doesn't return anything other than the list of mirrors checked. Just checked the web site listed under a2ps info and 4.13 is the current version. Works fine everywhere else. My cluephone number is 867-5309, ask for Jenn. Howard -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
