What sysadmin must do to run OS with damaged /lib/libc.so file ? / rsyslogd daemon logrotation / deny checking list of running processes

Posted by Virtual_Lotos on Server Fault See other posts from Server Fault or by Virtual_Lotos
Published on 2013-11-07T15:03:03Z Indexed on 2013/11/07 15:57 UTC
Read the original article Hit count: 164

Filed under:
|
|

What sysadmin must do to run OS with damaged /lib/libc.so file ?

In other words, how command interpreter should be configured to be able to run system with

corrupted /lib/libc.so file ?

Do I have to move it to /var catalog ?

Does the command interpreter must be statically compiled or have setuid attribute or perhaps must be a symbolic link to /bin/sh or must be no larger than 2MB ?


How to prevent a user from checking list of processes started by another user ? How do I forbid a user to see which processes are running by another user ?


What do I have to keep in mind when I want to make rsyslogd daemon logrotation ?

© Server Fault or respective owner

Related posts about linux

Related posts about process