Linux

2334 readers

1 users here now

Shit, just linux.

Use this community for anything related to linux for now, if it gets too huge maybe there will be some sort of meme/gaming/shitpost spinoff. Currently though… go nuts

founded 1 year ago

MODERATORS

[email protected]

Determining the efficacy of a restart from a bash script (Debian) (lemmy.world)

submitted 1 month ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

I should preface this by stating I am a novice in general when it comes to the linux world.

I'm trying to write a bash script that will run on an ordinary basis as a cron job. It's simple enough it just runs apt update -y apt upgrade -y apt autoclean every 24 hours. The issue is that I also would like to be able to schedule a restart automatically if a restart would be frugal. I don't really want to just rely on checking for /var/run/reboot-required, and the output from debian-goodies checkrestart seems to be pretty dated and incompatible with scripts in general. Would it be better to run systemctl status and check for degradation, and then schedule a restart based on that? Does anyone far smarter than me have a solution?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 1 month ago* (last edited 1 month ago) (2 children)

There's a package that handles most people's needs called unattended-upgrades. Has some options and some logic to do things like this. Check it out and let me know if you have any questions. Been using it on hundreds of servers for 5+ years.

[–] [email protected] 3 points 1 month ago (1 children)

I'm reading this again and had another thought. On an average Debian server reboot-required is really only ever triggered by kernel upgrades and those happen more often than you want but also not very often. They are also usually worth installing for either security or performance improvements.

It's usually ok to just set a convenient time for unattended-upgrades to run, let it watch for reboot-required and then reboot automatically. If your services can't handle starting at boot or turning off gracefully then you will have other problems anyway.

On the other hand, if even a few minutes of downtime every couple of months at a scheduled time is too much, just disable AUTO-REBOOT in the config file and do it by hand whenever it works for you. It's all good. Do what works best for you, that's the best part of Linux.

needs-restart is another great package that will check if package updates should restart any services to take effect and restart them if so. Goes nicely with unattended-upgrades

[–] [email protected] 2 points 1 month ago

On an average Debian server reboot-required is really only ever triggered by kernel upgrades and those happen more often than you want but also not very often.

Cries in Arch