当前位置: 技术问答>linux和unix
Redhat rpm -e glibc后系统无法登录
来源: 互联网 发布时间:2017-05-24
本文导语: 由于想在64位系统上重现安装32位的glic包,所以照网上的方法先卸载原来的glibc-2.5-42,命令是: rpm -e --allmatches --nodeps glibc-2.5-42 执行之后报了几个错: /lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directo...
由于想在64位系统上重现安装32位的glic包,所以照网上的方法先卸载原来的glibc-2.5-42,命令是:
rpm -e --allmatches --nodeps glibc-2.5-42
执行之后报了几个错:
/lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory
再登录的时候系统无法登录了:
Last login: Sun Jul 27 08:07:49 2014 from 10.198.22.183
/bin/bash: No such file or directory
Connection closed.
求大神帮忙分析原因,是不是要重装系统了?
rpm -e --allmatches --nodeps glibc-2.5-42
执行之后报了几个错:
/lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory
再登录的时候系统无法登录了:
Last login: Sun Jul 27 08:07:49 2014 from 10.198.22.183
/bin/bash: No such file or directory
Connection closed.
求大神帮忙分析原因,是不是要重装系统了?
|
rpm -e --allmatches --nodeps glibc-2.5-42
if glibc is removed, then most of programs will not be able to work. However if the glibc so is still in memory, everything should seems to work until you restart the server.
since the login prompt is offered, the kernel should be intact.
Reinstall if there is nothing important on the machine. SOS kit could help you recover files...
if glibc is removed, then most of programs will not be able to work. However if the glibc so is still in memory, everything should seems to work until you restart the server.
since the login prompt is offered, the kernel should be intact.
Reinstall if there is nothing important on the machine. SOS kit could help you recover files...