Three tips for improving the efficiency of Linux operation and maintenance management

Linux management efficiency is a manifestation of an administrator's ability to work. Here are three tips to help some less experienced administrators to complete the management of the system.

Administrators want to improve Linux management efficiency by following some management techniques. Here are three tips on Linux management efficiency: uninstalling unresponsive DVD drives, recovering problematic screens, and screen collaboration. I believe they will improve the efficiency of the administrator.

Tips 1: Uninstalling Unresponsive DVD Drives

Network Novice Experience: Pressing the Eject button on the server (running Redmond-based operating system
) DVD drive , it will pop up immediately. He then complained that in most enterprise Linux servers, if a process is running in that directory, the popup will not happen. As a long-time Linux administrator, I will reboot the machine. If I don't know what is running and why I don't release the DVD drive, I will eject the disk. But this is very inefficient.

The following describes how to find the process to keep the DVD drive and easily eject the DVD drive: first simulate. Put the disk in the DVD drive, open a terminal, and mount the DVD drive:

# mount /media/cdrom# cd /media/cdrom# while [ 1 ]; do echo "All your drives are belong to Us! "; sleep 30; done

Now open the second terminal and try to eject the DVD drive:

# eject will get the following message: umount: /media/cdrom: device is busy< Br>

Before releasing the device, let us find out who is using it.

# fuser /media/cdrom

The process is running, and the failure to eject the disk is actually our fault. Now, if you are the root user, you can terminate the process at will:

# fuser -k /media/cdrom Now you can finally unmount the drive: # eject fuser is normal.

Tips 2: Recover the screen where the problem occurred

Try the following:

# cat /bin/cat

Note! The terminal wants to be like garbage. Everything you enter is very messy. So what should I do? Enter reset. However, entering reset is too close to typing reboot or shutdown. Scared to sweat, — especially when performing this operation on a production machine. Don't worry, the machine won't restart when you do this. Continue:

# reset

The screen is now back to normal. This is much better than logging in again after closing the window, especially if you have to go through 5 machines and SSH to get to the machine.