Thanks John VV, I have now tried what you suggest, but the 3.3.2 Makefile has no uninstall target.
I can find no reference on Python website to uninstalling Python.
I tried installing 2.7.8 from source, to see if I could overwrite the damage, but got no solution.
Incredibly, the 2.7.8 Makefile has no uninstall target either, and no reference to anything that I
can identify as being like uninstall.
The only help I read about is to use the package managers, but since Yum & RPM are out of order I
am at a loss.
I straced an rpm operation to see if python was the obvious problem. The last lines of the tracefile was
Code:
open("/var/lib/rpm/.dbenv.lock", O_RDWR|O_CREAT, 0644) = 3
umask(022) = 022
fcntl(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}
.. which I guess to be trying to do something with locks on the rpm database
I straced a yum operation and got
Code:
open("/var/lib/rpm/.dbenv.lock", O_RDWR|O_CREAT, 0644) = 3
umask(022) = 022
fcntl(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}
.. not surprisingly, hung in the same place. I don't know if this gets me anywhere. I am fishing
in unknown waters now.
Checked out what was causing the lock, it was dnf. I killed the dnf process, removed dnf from systemctl,
and tried both the rpm and yum operations again. No file locks anymore, but the tracefile on both end
as follows
Code:
mmap(NULL, 286720, PROT_READ|PROT_WRITE, MAP_SHARED, 5, 0) = 0x7f11e1432000
sched_yield() = 0
futex(0x7f11e1432334, FUTEX_WAIT, 11, NULL
.. which I understand is an incomplete system call futex(). Something about locking and releasing
shared memory resources?
Quote:
|
splash splash, it's dark in here!
|
Steve S
