Le Mardi 03 Avril 2001 11:30, vous avez écrit :
> On Tue, Apr 03, 2001 at 03:11:00PM +0800, R.I.P. Deaddog wrote:
> > Yes, touch /etc/ld.so.preload was dangerous.......... once I have a typo
> > in /etc/ld.so.preload and made the whole system unusable (before I found
> > a way to boot with rescue floppy).
>
> That's a drastic means to recover. If you are confident that you can
> reproduce /etc/ld.so.preload (i.e. have a copy of it, or can remember
> what was in it, etc.) recovering from a bad /etc/ld.so.preload is as
> simple as doing a ">/etc/ld.so.preload" from a bash shell. That
> assumes you are logged in somewhere and have a bash shell running.
>
> The ">/etc/ld.so.preload" "zeros" (i.e. empties out) a file.
>
> b.
The package doesn't touch to the /etc/ld.so.preload file it only install the
libsafe package in /lib and exemple file.
But if you have allready the libsafe 1.3 running on our system you need to
install libsafe 2.0 in the same time (rpm -i and not -u) and after change the
reference and the ld.so.preload file.
In fact you will have the same problem if you remove the libsafe 1.3 package,
i don't think it's a problem of uprade.
I think it's msec level who change the /etc/ld.so.preload file.
Vince
