As documented here, if there is a core update, the computer will automatically update, then reboot.
I wish to have automatic updates on, but do not wish to have the machine automatically reboot. Is there a way to do this?
As documented here, if there is a core update, the computer will automatically update, then reboot.
I wish to have automatic updates on, but do not wish to have the machine automatically reboot. Is there a way to do this?
I was trying to track down the Snappy Ubuntu Core source code and the closest I could find was this which has an accepted answer that I find unacceptable. With the source code many developers seeking to turn off auto-updates might be able to accomplish a goal akin to your own.
The second best solution for them, and perhaps yourself, is to find the name of the binary that performs auto-updating. Let's say for example it is called a. Rename it to b. Replace a with a simple program that displays "Hello World". During system boot call b in startup scripts.
Basically whenever you want to update your OS (or "Store" as they like to call it) at your convenience simply reboot your machine. After the update it will reboot again. On the second reboot when b is called the first reboot already updated the applications (called "snaps") so the second reboot would perform without an update.
Whenever Ubuntu tries to run auto-updates behind your back, it will simply be running a new program that writes "Hello World" to /var/log/syslog.
I'm not using Raspberry Pi 2 so I can't find the name of the auto-update program that needs to be renamed to "b". Hopefully someone else does use it and can provide the name.
As far as I know there is no way to prevent/or let Ubuntu don't reboot after upgrading automatically.
But as a workaround you can enable the rootpw flag in your sudoers, to making sudo reboot which trigger at the end of the upgrade (I guess) ask for the root password instead of user password. open it via visudo
Defaults rootpw
Or if the upgrade process is doing like this upgrade && reboot as an example it will ask you for password for upgrade part command and will execute next command with cached your password. you may need to reset this catch so it will ask for password again when second reboot wants to trigger.
sudo -K
or you can set timestamp_timeout parameter to let sudo ask password for every commands invoking by sudo.