Unattended-Upgrade::Automatic-Reboot default value
In my /etc/apt/apt.conf.d/50unattended-upgrades i found this:
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot "false";
The issue is that I don't know what the default value is and so if I need to uncomment the line (I don't want my server to reboot btw).
Should I uncomment the line by safety? Are there further actions to perform after doing that?
16.04 server reboot
asked Nov 5 '17 at 22:25
StringerStringer
1136
add a comment |
In my /etc/apt/apt.conf.d/50unattended-upgrades i found this:
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot "false";
The issue is that I don't know what the default value is and so if I need to uncomment the line (I don't want my server to reboot btw).
Should I uncomment the line by safety? Are there further actions to perform after doing that?
16.04 server reboot
asked Nov 5 '17 at 22:25
StringerStringer
1136
You could test it be putting this file there manually as testsudo touch /car/run/reboot-required.. usually default should not be an autoreboot
– derHugo
Nov 5 '17 at 22:50
Test it and it did nothing. Thanks.
– Stringer
Nov 5 '17 at 23:18
add a comment |
In my /etc/apt/apt.conf.d/50unattended-upgrades i found this:
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot "false";
The issue is that I don't know what the default value is and so if I need to uncomment the line (I don't want my server to reboot btw).
Should I uncomment the line by safety? Are there further actions to perform after doing that?
16.04 server reboot
asked Nov 5 '17 at 22:25
StringerStringer
1136
In my /etc/apt/apt.conf.d/50unattended-upgrades i found this:
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot "false";
The issue is that I don't know what the default value is and so if I need to uncomment the line (I don't want my server to reboot btw).
Should I uncomment the line by safety? Are there further actions to perform after doing that?
16.04 server reboot
16.04 server reboot
asked Nov 5 '17 at 22:25
StringerStringer
1136
asked Nov 5 '17 at 22:25
StringerStringer
1136
asked Nov 5 '17 at 22:25
StringerStringer
1136
asked Nov 5 '17 at 22:25
StringerStringer
1136
asked Nov 5 '17 at 22:25
StringerStringer
1136
1136
You could test it be putting this file there manually as testsudo touch /car/run/reboot-required.. usually default should not be an autoreboot
– derHugo
Nov 5 '17 at 22:50
Test it and it did nothing. Thanks.
– Stringer
Nov 5 '17 at 23:18
add a comment |
You could test it be putting this file there manually as testsudo touch /car/run/reboot-required.. usually default should not be an autoreboot
– derHugo
Nov 5 '17 at 22:50
Test it and it did nothing. Thanks.
– Stringer
Nov 5 '17 at 23:18
You could test it be putting this file there manually as test
sudo touch /car/run/reboot-required .. usually default should not be an autoreboot– derHugo
Nov 5 '17 at 22:50
You could test it be putting this file there manually as test
sudo touch /car/run/reboot-required .. usually default should not be an autoreboot– derHugo
Nov 5 '17 at 22:50
Test it and it did nothing. Thanks.
– Stringer
Nov 5 '17 at 23:18
Test it and it did nothing. Thanks.
– Stringer
Nov 5 '17 at 23:18
add a comment |
2 Answers
2
active
oldest
votes
If you don't want it to auto-reboot, make that section look like this:
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
Unattended-Upgrade::Automatic-Reboot "false";
I have it set that way and it works.
This page says that not rebooting is the default, but I'm pretty sure that's wrong. I think the first time my system autoinstalled a kernel (before I changed the config), it rebooted. But in either case, the config above will prevent it.
answered Nov 5 '17 at 23:04
Organic MarbleOrganic Marble
11k63458
Thanks, I'll take the safe path then. From what I understand only a kernel update needs a reboot and it is disable by default (if you have choosen auto install of security packages). Anyway I'll go the safe path.
– Stringer
Nov 5 '17 at 23:14
5
I don't think it's wrong, my systems don't reboot automatically unless I told them to.
– Reinier Post
Nov 14 '17 at 18:44
That could well be, I was experimenting with a lot of different options.
– Organic Marble
Nov 14 '17 at 19:15
1
100% with @ReinierPost - I have many servers in production; one rebooted automatically and the rest did not, which led me to this answer. All servers except the one that rebooted have it commented out thus using the default, which is to not reboot. The one that rebooted had it set to "true", which I have now fixed by commenting it out.
– zaTricky
Oct 3 '18 at 8:12
1
default value is to NOT reboot. libre-software.net/ubuntu-automatic-updates and linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu Also, See serverfault.com/a/606852/399723 if you're using debian-7=wheezy or earlier AKA ubuntu 13.10 or earlier, because you'll need an additional package for this setting to work correctly.
– SherylHohman
Nov 12 '18 at 17:03
add a comment |
The default for automatically rebooting after unattended-upgrades is FALSE.
You can confirm on your own system by looking where the default value is stored, in the script itself:
grep 'Automatic-Reboot"' /usr/bin/unattended-upgrade
The default could change with a software upgrade, although that seems unlikely. To be certain your systems don't reboot by after automatic upgrades, explicitly disable rebooting in your configuration.
answered 10 hours ago
Mark StosbergMark Stosberg
2,23811526
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f973318%2funattended-upgradeautomatic-reboot-default-value%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you don't want it to auto-reboot, make that section look like this:
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
Unattended-Upgrade::Automatic-Reboot "false";
I have it set that way and it works.
This page says that not rebooting is the default, but I'm pretty sure that's wrong. I think the first time my system autoinstalled a kernel (before I changed the config), it rebooted. But in either case, the config above will prevent it.
answered Nov 5 '17 at 23:04
Organic MarbleOrganic Marble
11k63458
Thanks, I'll take the safe path then. From what I understand only a kernel update needs a reboot and it is disable by default (if you have choosen auto install of security packages). Anyway I'll go the safe path.
– Stringer
Nov 5 '17 at 23:14
5
I don't think it's wrong, my systems don't reboot automatically unless I told them to.
– Reinier Post
Nov 14 '17 at 18:44
That could well be, I was experimenting with a lot of different options.
– Organic Marble
Nov 14 '17 at 19:15
1
100% with @ReinierPost - I have many servers in production; one rebooted automatically and the rest did not, which led me to this answer. All servers except the one that rebooted have it commented out thus using the default, which is to not reboot. The one that rebooted had it set to "true", which I have now fixed by commenting it out.
– zaTricky
Oct 3 '18 at 8:12
1
default value is to NOT reboot. libre-software.net/ubuntu-automatic-updates and linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu Also, See serverfault.com/a/606852/399723 if you're using debian-7=wheezy or earlier AKA ubuntu 13.10 or earlier, because you'll need an additional package for this setting to work correctly.
– SherylHohman
Nov 12 '18 at 17:03
add a comment |
If you don't want it to auto-reboot, make that section look like this:
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
Unattended-Upgrade::Automatic-Reboot "false";
I have it set that way and it works.
This page says that not rebooting is the default, but I'm pretty sure that's wrong. I think the first time my system autoinstalled a kernel (before I changed the config), it rebooted. But in either case, the config above will prevent it.
answered Nov 5 '17 at 23:04
Organic MarbleOrganic Marble
11k63458
Thanks, I'll take the safe path then. From what I understand only a kernel update needs a reboot and it is disable by default (if you have choosen auto install of security packages). Anyway I'll go the safe path.
– Stringer
Nov 5 '17 at 23:14
5
I don't think it's wrong, my systems don't reboot automatically unless I told them to.
– Reinier Post
Nov 14 '17 at 18:44
That could well be, I was experimenting with a lot of different options.
– Organic Marble
Nov 14 '17 at 19:15
1
100% with @ReinierPost - I have many servers in production; one rebooted automatically and the rest did not, which led me to this answer. All servers except the one that rebooted have it commented out thus using the default, which is to not reboot. The one that rebooted had it set to "true", which I have now fixed by commenting it out.
– zaTricky
Oct 3 '18 at 8:12
1
default value is to NOT reboot. libre-software.net/ubuntu-automatic-updates and linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu Also, See serverfault.com/a/606852/399723 if you're using debian-7=wheezy or earlier AKA ubuntu 13.10 or earlier, because you'll need an additional package for this setting to work correctly.
– SherylHohman
Nov 12 '18 at 17:03
add a comment |
If you don't want it to auto-reboot, make that section look like this:
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
Unattended-Upgrade::Automatic-Reboot "false";
I have it set that way and it works.
This page says that not rebooting is the default, but I'm pretty sure that's wrong. I think the first time my system autoinstalled a kernel (before I changed the config), it rebooted. But in either case, the config above will prevent it.
answered Nov 5 '17 at 23:04
Organic MarbleOrganic Marble
11k63458
If you don't want it to auto-reboot, make that section look like this:
// Automatically reboot *WITHOUT CONFIRMATION*
// if the file /var/run/reboot-required is found after the upgrade
Unattended-Upgrade::Automatic-Reboot "false";
I have it set that way and it works.
This page says that not rebooting is the default, but I'm pretty sure that's wrong. I think the first time my system autoinstalled a kernel (before I changed the config), it rebooted. But in either case, the config above will prevent it.
answered Nov 5 '17 at 23:04
Organic MarbleOrganic Marble
11k63458
answered Nov 5 '17 at 23:04
Organic MarbleOrganic Marble
11k63458
answered Nov 5 '17 at 23:04
Organic MarbleOrganic Marble
11k63458
answered Nov 5 '17 at 23:04
Organic MarbleOrganic Marble
11k63458
11k63458
Thanks, I'll take the safe path then. From what I understand only a kernel update needs a reboot and it is disable by default (if you have choosen auto install of security packages). Anyway I'll go the safe path.
– Stringer
Nov 5 '17 at 23:14
5
I don't think it's wrong, my systems don't reboot automatically unless I told them to.
– Reinier Post
Nov 14 '17 at 18:44
That could well be, I was experimenting with a lot of different options.
– Organic Marble
Nov 14 '17 at 19:15
1
100% with @ReinierPost - I have many servers in production; one rebooted automatically and the rest did not, which led me to this answer. All servers except the one that rebooted have it commented out thus using the default, which is to not reboot. The one that rebooted had it set to "true", which I have now fixed by commenting it out.
– zaTricky
Oct 3 '18 at 8:12
1
default value is to NOT reboot. libre-software.net/ubuntu-automatic-updates and linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu Also, See serverfault.com/a/606852/399723 if you're using debian-7=wheezy or earlier AKA ubuntu 13.10 or earlier, because you'll need an additional package for this setting to work correctly.
– SherylHohman
Nov 12 '18 at 17:03
add a comment |
Thanks, I'll take the safe path then. From what I understand only a kernel update needs a reboot and it is disable by default (if you have choosen auto install of security packages). Anyway I'll go the safe path.
– Stringer
Nov 5 '17 at 23:14
5
I don't think it's wrong, my systems don't reboot automatically unless I told them to.
– Reinier Post
Nov 14 '17 at 18:44
That could well be, I was experimenting with a lot of different options.
– Organic Marble
Nov 14 '17 at 19:15
1
100% with @ReinierPost - I have many servers in production; one rebooted automatically and the rest did not, which led me to this answer. All servers except the one that rebooted have it commented out thus using the default, which is to not reboot. The one that rebooted had it set to "true", which I have now fixed by commenting it out.
– zaTricky
Oct 3 '18 at 8:12
1
default value is to NOT reboot. libre-software.net/ubuntu-automatic-updates and linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu Also, See serverfault.com/a/606852/399723 if you're using debian-7=wheezy or earlier AKA ubuntu 13.10 or earlier, because you'll need an additional package for this setting to work correctly.
– SherylHohman
Nov 12 '18 at 17:03
Thanks, I'll take the safe path then. From what I understand only a kernel update needs a reboot and it is disable by default (if you have choosen auto install of security packages). Anyway I'll go the safe path.
– Stringer
Nov 5 '17 at 23:14
Thanks, I'll take the safe path then. From what I understand only a kernel update needs a reboot and it is disable by default (if you have choosen auto install of security packages). Anyway I'll go the safe path.
– Stringer
Nov 5 '17 at 23:14
5
5
I don't think it's wrong, my systems don't reboot automatically unless I told them to.
– Reinier Post
Nov 14 '17 at 18:44
I don't think it's wrong, my systems don't reboot automatically unless I told them to.
– Reinier Post
Nov 14 '17 at 18:44
That could well be, I was experimenting with a lot of different options.
– Organic Marble
Nov 14 '17 at 19:15
That could well be, I was experimenting with a lot of different options.
– Organic Marble
Nov 14 '17 at 19:15
1
1
100% with @ReinierPost - I have many servers in production; one rebooted automatically and the rest did not, which led me to this answer. All servers except the one that rebooted have it commented out thus using the default, which is to not reboot. The one that rebooted had it set to "true", which I have now fixed by commenting it out.
– zaTricky
Oct 3 '18 at 8:12
100% with @ReinierPost - I have many servers in production; one rebooted automatically and the rest did not, which led me to this answer. All servers except the one that rebooted have it commented out thus using the default, which is to not reboot. The one that rebooted had it set to "true", which I have now fixed by commenting it out.
– zaTricky
Oct 3 '18 at 8:12
1
1
default value is to NOT reboot. libre-software.net/ubuntu-automatic-updates and linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu Also, See serverfault.com/a/606852/399723 if you're using debian-7=wheezy or earlier AKA ubuntu 13.10 or earlier, because you'll need an additional package for this setting to work correctly.
– SherylHohman
Nov 12 '18 at 17:03
default value is to NOT reboot. libre-software.net/ubuntu-automatic-updates and linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu Also, See serverfault.com/a/606852/399723 if you're using debian-7=wheezy or earlier AKA ubuntu 13.10 or earlier, because you'll need an additional package for this setting to work correctly.
– SherylHohman
Nov 12 '18 at 17:03
add a comment |
The default for automatically rebooting after unattended-upgrades is FALSE.
You can confirm on your own system by looking where the default value is stored, in the script itself:
grep 'Automatic-Reboot"' /usr/bin/unattended-upgrade
The default could change with a software upgrade, although that seems unlikely. To be certain your systems don't reboot by after automatic upgrades, explicitly disable rebooting in your configuration.
answered 10 hours ago
Mark StosbergMark Stosberg
2,23811526
add a comment |
The default for automatically rebooting after unattended-upgrades is FALSE.
You can confirm on your own system by looking where the default value is stored, in the script itself:
grep 'Automatic-Reboot"' /usr/bin/unattended-upgrade
The default could change with a software upgrade, although that seems unlikely. To be certain your systems don't reboot by after automatic upgrades, explicitly disable rebooting in your configuration.
answered 10 hours ago
Mark StosbergMark Stosberg
2,23811526
add a comment |
The default for automatically rebooting after unattended-upgrades is FALSE.
You can confirm on your own system by looking where the default value is stored, in the script itself:
grep 'Automatic-Reboot"' /usr/bin/unattended-upgrade
The default could change with a software upgrade, although that seems unlikely. To be certain your systems don't reboot by after automatic upgrades, explicitly disable rebooting in your configuration.
answered 10 hours ago
Mark StosbergMark Stosberg
2,23811526
The default for automatically rebooting after unattended-upgrades is FALSE.
You can confirm on your own system by looking where the default value is stored, in the script itself:
grep 'Automatic-Reboot"' /usr/bin/unattended-upgrade
The default could change with a software upgrade, although that seems unlikely. To be certain your systems don't reboot by after automatic upgrades, explicitly disable rebooting in your configuration.
answered 10 hours ago
Mark StosbergMark Stosberg
2,23811526
answered 10 hours ago
Mark StosbergMark Stosberg
2,23811526
answered 10 hours ago
Mark StosbergMark Stosberg
2,23811526
answered 10 hours ago
Mark StosbergMark Stosberg
2,23811526
2,23811526
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f973318%2funattended-upgradeautomatic-reboot-default-value%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You could test it be putting this file there manually as test
sudo touch /car/run/reboot-required.. usually default should not be an autoreboot– derHugo
Nov 5 '17 at 22:50
Test it and it did nothing. Thanks.
– Stringer
Nov 5 '17 at 23:18