At 09:37 AM 6/19/2007, Claude Jones wrote:
<CJ>>>>>We're all busy, Eric. You can't take the time to glance at two days
worth of list traffic, but I should summarize my efforts of over 36 hours
for you.<<<<<
Sorry, I didn't mean for it to sound like that. Nor did I intend for you
to go through the effort you just did (thanks!). I thought a
one-short-paragraph summary would do it.
I was unable to access the list archives the last few times I tried it,
don't know why (doesn't have anything to do with Linux, have tried and
failed on both Windows and Linux boxes) but this morning I was able to get
through to it and found one of the threads you mentioned, the one about
"Package managers gone haywire".
Your notes about SELinux are noted, however I have had SELinux disabled all
along. I just checked it and it's still disabled.
<CJ>>>>>you seem to have the time to drive to the next city over if you
must<<<<<
Actually I don't, nto really ... that's the problem. But, as you say, if I
"must" then I guess I have to take the time whether I have it or not...
I will try all the things you tried, although I am a little nervous about
deleting all the __db.00x files when three of the four of them are still
open as reported by lsof. I think that's caused by having to kill the rpm
process with SIGKILL, which tends not to kill things very cleanly...
I've been toying with the notion of just rebooting the machine remotely
with "reboot"... I suppose the worst that can happen then is I'll have to
drive over to the colo facility and fix it if it doesn't reboot properly...
Eric Poole
Burgoyne, Nolet & Poole, Inc.
www.bnpconsulting.com
