![]() ![]() You should have knowledge of the process. Don’t go blindly removing stuff here, please. You should also check the content of /etc/systemd/nf file and make sure that the value of Storage is set to either auto or persistent.ĭo you find something suspicious in the logs? Is there a process/service refusing to stop? If yes, investigate if you could remove it without side effects or if you could reconfigure it. If it doesn’t, create it: sudo mkdir /var/log/journal If there are no journal logs, please make sure that your distribution uses systemd.Įven on some Linux distributions with systemd, the journal logs are not activated by default. ![]() The commands and steps here are valid for any Linux distribution that uses systemd (most of them do). I am using Ubuntu here which uses systemd. Change the default waiting period before your system force stops the running processes.Check which process/service is taking too long and if you can remove or reconfigure it to behave properly.If your system is taking too long in shutting down, you can do the following: In fact, in some cases, you would see a message like ‘a stop job is running’ on the black screen. I recommend reading about sigterm vs sigkill to understand the difference. After this time period, it sends the kill signal to force stop all the remaining running processes and shuts down the system. This could cause a delay to the shutdown process as your system will wait for the running processes to stop for a predefined time period. Some processes misbehave and they ignore the sigterm and keep on running. When you shut down your Linux system, it sends the sigterm and politely asks the running processes to stop. I hope you are a tad bit familiar with the sigterm and sigkill concept. Your Linux system is taking too long to shut down? Here are the steps you can take to find out what is causing the delayed shutdown and fix the issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |