crontab’s @reboot only works for root?
man 5 crontab is pretty clear on how to use crontab to run a script on boot:
reboot
Save entire process for continuation after reboot
I developed an algorithm for a fairly hard problem in mathematics which is likely to need several months to finish. As I have limited resources only, I started this on my Ubuntu 12.04 (x86) laptop. Now I want to install some updates and actually restart the laptop (the “please reboot” message is just annoying).
Why are reboot, shutdown and poweroff symlinks to systemctl?
In Arch Linux, if I do ls -l in /sbin, I can see that reboot, shutdown and poweroff are all symlinks to /usr/bin/systemctl. But issuing reboot, shutdown and systemctl commands obviously does not all have the same behaviour.
Why does reboot and poweroff require root privileges?
What security risk is posed by not requiring this to have root privileges? The GUI provides a way for any user to shut off or restart, so why do the terminal commands need to be run as root?
Reducing shutdown timeout for “a stop job is running”
I’ve got node.js and pm2 installed on a Pi (Raspbian). PM2 was configured to start via pm2 startup and the init scripts it creates. Sometimes when I reboot, shutdown hangs for a few minutes on:
How long has my Linux system been running?
Is there a command I can type in a terminal that will tell me the last time a machine was rebooted?
How to continue a script after it reboots the machine?
I’m writing a shell script in bash. At some point in the script, it detects that the machine needs to be rebooted before continuing. It issues: