Linux server system maintenance skills detailed

Faced with the current hot Linux system, many users will install Linux as a server, and the server is relatively stable and secure than the Windwos server. However, if a worker wants to do something good, he must first sharpen his weapon. A stable and secure Linux server is still inseparable from reasonable and timely maintenance. Therefore, today's issue is the maintenance skills of the Linux server system; this question will introduce the maintenance skills of the Linux server system in detail, and help users solve problems. The maintenance skills of the specific Linux server system are as follows:

1. Create a floppy disk boot disk.

Although floppy disks are used less and less, there are still floppy drives in some large servers, such as IBM's servers. This is mainly because sometimes complex problems can be solved by floppy drives. For this reason, after deploying the Linux server, it is best to create a floppy disk boot disk, which can be used to save the emergency when it is needed.

If sometimes the system administrator may encounter some inexplicable problems during the installation process, such as installing many times in the middle, it can not be installed successfully. This is most likely due to a problem with installing the image. At this point the system administrator needs a modified floppy image. Although this situation is relatively rare, it is relatively easy to encounter when deploying a relatively large server. When this happens, the system administrator should not blindly download the installation image or take other time-consuming and laborious actions. You can use the standard installation floppy disk to start the installation. Maybe you can solve the failure during the installation process.

It is precisely because the floppy disk boot disk has a very important position in the maintenance of Linux servers. RedHat also provides many ways to create a floppy disk boot disk. Such as creating a floppy boot disk during installation, and so on. These boot disk creation methods are more conventional, and the author will not expand the description. Here I am going to introduce you to a method of creating a floppy disk boot disk in the Windows environment. This is mainly because most system administrators still have a computer with a Windwos operating system. Instead, just use the Linux operating system as a server. The server is placed in a fixed place, and some are not even equipped with a display. For this reason, it is more troublesome to create a floppy disk on a Linux server. So I am here to push the Winwos client to create a floppy boot disk. The tools used here only need the RedHat installation disk.

The system administrator first puts the Linux installation disk into the CD-ROM drive of the Windwos client. Then open the DOS interface of the Microsoft operating system and go to the directory where the CD-ROM is located. In the RedHat installation disk, there is a directory called dosutils, in this directory there is an executable command file called rawh. This is the file it uses to create the boot disk. After the floppy disk is ready, execute this command. Then this command will ask for the floppy disk image, enter the full path name, and insert the prepared floppy disk into the floppy drive. When the application determines to you which floppy disk drive you need to write the boot image to, you can specify the floppy boot initiator, which is usually a:.

In addition, if you boot from a floppy disk, it is similar to booting from a CD. If the installation is initiated using a floppy disk, the user may be asked to confirm the language used, the type of keyboard selected, the type of mouse selected, and so on. At this point, the Linux bootloader is not as strong as the Windows bootloader and does not automatically identify the connected device. To do this, you need to specify the keyboard and mouse type used by the system administrator during the boot process. After the next device change, if you change the mouse from three buttons to two buttons, or if the mouse's excuse changes, you still need to reconfigure. It can be seen that at this point, the Linux operating system is not as good as the bootloader of the Windows operating system. But in general, the floppy boot disk function of the Linux operating system is still very powerful. For this reason, I strongly recommend that system administrators need to create a floppy disk boot disk when deploying a Linux server. Since the floppy disk boot disk is prone to be bad, it is also possible to create one more.

Second, let the software package keep the latest version.

The Linux server package is constantly being upgraded like the patch for the Windwos operating system. The upgrade of Linux server software has two main purposes. One is to enhance the functionality of the software, and the other is to resolve some known security vulnerabilities. If RedHat knows about new security vulnerabilities, it will immediately research and develop the corresponding solution, and then solve it in the new version of the software package. To this end, the system administrator must keep abreast of the latest information about the software package and update the software package in time to keep the software package up to date.

So how do system administrators know the latest software versions and security vulnerabilities? The author recommends a support site for RedHat, shown above. Under normal circumstances, RedHat will find the relevant solution in the shortest time after receiving the notification of the security vulnerability, and publish and connect to the latest version of the package download address on this technical support platform. In general, more than 90% of the latest versions of the software under the Linux operating system can be found on this website. So system administrators need to pay attention to this website every day to get the latest version information and security vulnerability information of the software package. Upgrade the software package in a timely manner if necessary.

Third, to achieve a good planning partition.

The partitioning plan for the Linux operating system is different from the partitioning plan for the Microsoft operating system. The latter partition planning has little impact on its performance. However, the partitioning plan of the Linux operating system is different, which has a great impact on the performance of the server. In fact, I like to compare the partition of the Linux operating system to the tablespace planning in the Oracle database. The two of them have the same effect. The quality of the plan will directly affect the performance of its operation. And only need to make some adjustments during deployment, the impact on subsequent performance is very significant.

If I use the Linux operating system as a server, I will consider placing some special directories on different partitions, which will improve the performance and security of subsequent servers. For example, you can place the /tmp directory and the /home directory on different partitions; for example, you can place the /var and /usr directories on different partitions. If hardware conditions permit, it is best to place the /var directory on a separate partition. Because these directories have their special uses and are used more frequently. If they are placed separately, the reading efficiency of the data can be improved, and the space contention between each other can be reduced.

In addition, the exchange partition needs special attention. The swap partition under the Linux operating system is like virtual memory under the Windows operating system. However, there are significant differences between the two under subsequent adjustments. For example, in the Windows operating system, if the virtual memory is not enough, you can adjust it in the system properties and advanced tabs. And even if this virtual memory is subsequently adjusted, the subsequent increased space has the same performance as the original space. In the Linux operating system, if the virtual space is later found to affect the performance of the application, it will even affect the installation of the application. At this point, if you want to adjust, the process of adjustment is much more troublesome than the Windwos operating system. If you need to reinstall the operating system or re-partition a hard disk from the hard disk to use as a swap partition. However, if a space is not divided into virtual memory on the hard disk afterwards, the subsequent addition of the space is not as efficient as the space specified in the installation process. For this reason, unless this Linux server is already in use, I would recommend expanding the number of swap partitions by reinstalling.

So it's best to be able to plan and work with the relevant partitions between installing and deploying Linux servers. The main thing to consider is to store those directories on different paths, how much swap partition space to set, and so on. Typically, an experienced system administrator can plan this partition appropriately based on the application services to be deployed next. This is also a big difference between senior system engineers and rookie system administrators. Because rookie-level system administrators may only use the default configuration in the operating system. It is also possible to use this default configuration directly, but the performance of subsequent servers will be affected. After the partition is set, it is difficult to adjust later. Even if the adjustment is made, its performance is not as good as expected. Therefore, it is necessary to make a zoning plan in advance.

4. Turn off unwanted services.

As with the Windwos system, the system will start many services after installation. Some of these services are required by the operating system or application. But some do not need to be activated. If it is started, it will bring certain security risks to the operating system. To do this, the system administrator needs to view the services it runs after deploying the Linux operating system. Then turn off some unwanted services as needed. To this end, system administrators must have the ability to determine which services are required and which services can be turned off. At this point, the system administrator can refer to the description of some applications and combine their own work experience to make judgments.