At 11:54 AM 2/2/2003, Jacques A. Vidrine wrote:
> Ok, I admit, no matter how it happened, an application using the wrong libcWell, things were definitely picking /usr/lib/libc.so.4 over anything in compat. Should sysinstall have nuked my /usr/lib/libc if it was putting the correct one in compat?
> is a bad thing.
>
> But, how are things supposed to work?
Apps that need the old libc.so.4 will find it in
/usr/lib/compat/libc.so.4 (or /usr/lib/libc.so.4 if you didn't remove
it, for that matter).
> In any case, a system lockup or being able to crash other user's processes
Well, after I recompiled httpd (which did have a single process owned by root) and rebooted, nothing at all owned by root touched anything that was compiled under 4.x. Non-privileged regular users owned the process owned by analog, which caused the same behavior. Me running analog under my normal account could kill processes owned by "nobody" with segfaults.> just by having the wrong libc shouldn't be possible no matter what happens.Probably not, although if you have processes running as root and using the `wrong' libc, all bets are off.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
