


Teach you how to set up the server to automatically restart using Linux
As programmers, we have all used Linux. We all know that Linux is mainly used for servers. In this article, we will teach you a technique to set up automatic server restart under Linux. I hope it will be useful for everyone's work.
The steps are as follows:
The steps to automatically restart at 3 a.m. on the 1st of each month are as follows:
1. Log in with the root account;
2. Open Terminal window;
3. Enter "crontab -e"
4. Press the Insert key.
5. Enter "0 3 1 * * reboot"
6. Press the esc key.
7. Enter ":wq" and press Enter.
The above input content can be queried through the "crontab -l" command.
Automatically restart at 3 a.m. every Monday
1. Log in with the root account;
2.Open the terminal window;
3.Enter " crontab -e"
4. Press the Insert key.
5. Enter "0 3 * * 1 reboot"
6. Press the esc key.
7. Enter ":wq" and press Enter.
The above input content can be queried through the "crontab -l" command.
Linux system scheduled restart
After successfully logging in to the background using the SSH tool, run the following command: crontab -e
Then insert the following content into the document as needed:
0 4 * * * /sbin/reboot (0 4 means restarting at 4 am every day.. 0 3 means 3 am..)
: After saving and exiting wq, execute the following command to restart the crond service. Yes.
/sbin/service crond stop //Close the service
/sbin/service crond restart //Restart the service
/sbin/service crond reload //Reload Enter the configuration
You can also start this service automatically when the system starts:
Add at the end of the /etc/rc.d/rc.local script:
/sbin/service crond start
Now that the Cron service is already in the process, we can use this service. The Cron service provides the following interfaces for everyone to use:
1. Directly use the crontab command to edit
The cron service provides the crontab command to set the cron service. The following are some parameters and instructions for this command:
crontab -u / /Set the cron service of a certain user. Generally, the root user needs this parameter when executing this command.
crontab -l //List the details of the cron service of a certain user.
crontab -r //Delete the cron service of each user
crontab -e //Edit the cron service of a certain user
For example, root checks his own cron settings: crontab -u root -l
Another example, root wants to delete fred's cron settings: crontab -u fred -r
When editing the cron service, the edited content has some formats and conventions, enter: crontab -u root -e
Enter vi editing mode. The edited content must conform to the following format: */1 * * * * ls >> /tmp/ls.txt
The first part of this format One part is the setting of the time, and the latter part is the command to be executed. If there are too many commands to be executed, you can write these commands into a script, and then just call the script directly here. Remember to write when calling The full path to the command. We have a certain agreement on setting the time. The first five * signs represent five numbers. The value range and meaning of the numbers are as follows:
minutes (0-59)
hours (0 -23)
Date(1-31)
Month(1-12)
Week(0-6)//0 represents Sunday
In addition to numbers, there are several special symbols: "*", "/" and "-", ",". * represents all numbers within the value range, "/" represents the meaning of every, "*/5 "represents every 5 units,"-"represents from a certain number to a certain number,","separates several discrete numbers. Here are a few examples to illustrate the problem:
Every morning at 6 o'clock
0 6 * * * echo "Good morning." >> /tmp/test.txt //Pay attention to simple echo , no output can be seen on the screen, because cron emails any output to the root mailbox.
Every two hours
0 */2 * * * echo "Have a break now." >> /tmp/test.txt
11pm Every two hours between 8am and 8am, 8am
0 23-7/2, 8 * * * echo "Have a good dream:)" >> /tmp/test.txt
On the 4th of every month and at 11 a.m. from Monday to Wednesday every week
0 11 4 * 1-3 command line
January 1 At 4 o'clock in the morning on the same day
0 4 1 1 * command line
Each time after editing a user's cron settings, cron automatically generates a new username under /var/spool/cron For files with the same name, the user's cron information is recorded in this file. This file cannot be edited directly and can only be edited with crontab -e. After cron starts, it reads this file every time and checks whether the commands in it need to be executed. Therefore, there is no need to restart the cron service after modifying this file.
2. Edit the /etc/crontab file to configure cron
The cron service not only needs to read all the files in /var/spool/cron once every minute, but also needs to read Once /etc/crontab, so we configure this file to also use the cron service to do something. Configuration with crontab is for a certain user, while editing /etc/crontab is a task for the system. The file format of this file is:
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO= root //If an error occurs or data is output, the data will be sent to this account as an email
HOME=/ //The path where the user runs, this is the root directory
# run-parts
01 * * * * root run-parts /etc/cron.hourly / /Execute the scripts in /etc/cron.hourly every hour
02 4 * * * root run-parts /etc/cron.daily //Execute the scripts in /etc/cron.daily every day
22 4 * * 0 root run-parts /etc/cron.weekly //Execute the script in /etc/cron.weekly every week
42 4 1 * * root run-parts /etc/ cron.monthly //Execute the script in /etc/cron.monthly every month
Please pay attention to the "run-parts" parameter. If you remove this parameter, you can write a certain script to be run later. The script name, not the folder name.
The above content is the technique for setting up the server to automatically restart under Linux. I hope that after reading this article, you will master this technique and be able to set up your own server to automatically restart.
Related recommendations:
How to automatically restart this program in python
##Tips for optimizing mysql on Linux
How to restart MySQL on various servers
The above is the detailed content of Teach you how to set up the server to automatically restart using Linux. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.

VS Code is available on Mac. It has powerful extensions, Git integration, terminal and debugger, and also offers a wealth of setup options. However, for particularly large projects or highly professional development, VS Code may have performance or functional limitations.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

How to back up VS Code configurations and extensions? Manually backup the settings file: Copy the key JSON files (settings.json, keybindings.json, extensions.json) to a safe location. Take advantage of VS Code synchronization: enable synchronization with your GitHub account to automatically back up all relevant settings and extensions. Use third-party tools: Back up configurations with reliable tools and provide richer features such as version control and incremental backups.
