How to disable release upgrade notification emails?
I have an Ubuntu 14.04 server installation that consistently sends a weekly email, from the root user, with the following content:
/etc/cron.weekly/update-notifier-common:
New release '16.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
How do I stop these emails, without upgrading to 16.04? Is there a method that doesn't involve disabling the script mentioned in the first line of the email?
Ideally I'd like to allow /etc/cron.weekly/update-notifier-common to continue to run, calling the /usr/lib/ubuntu-release-upgrader/release-upgrade-motd and /usr/lib/ubuntu-release-upgrader/check-new-release scripts, but stop new release messages. It would be useful for these scripts to still warn if my current release becomes EOL.
upgrade email notification
asked Oct 31 '16 at 9:35
ArronicalArronical
13.6k84993
add a comment |
I have an Ubuntu 14.04 server installation that consistently sends a weekly email, from the root user, with the following content:
/etc/cron.weekly/update-notifier-common:
New release '16.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
How do I stop these emails, without upgrading to 16.04? Is there a method that doesn't involve disabling the script mentioned in the first line of the email?
Ideally I'd like to allow /etc/cron.weekly/update-notifier-common to continue to run, calling the /usr/lib/ubuntu-release-upgrader/release-upgrade-motd and /usr/lib/ubuntu-release-upgrader/check-new-release scripts, but stop new release messages. It would be useful for these scripts to still warn if my current release becomes EOL.
upgrade email notification
asked Oct 31 '16 at 9:35
ArronicalArronical
13.6k84993
It seems to check whether/usr/lib/ubuntu-release-upgrader/release-upgrade-motdexists and runs it if not.
– Arronical
Oct 31 '16 at 9:41
sorry yes I looked, and that runs/usr/lib/ubuntu-release-upgrader/check-new-releaseif there is a new release, and that is a python3 script that I am guessing is responsible for bothering you... but I have 16.10 so maybe it is not the same
– Zanna
Oct 31 '16 at 9:49
add a comment |
I have an Ubuntu 14.04 server installation that consistently sends a weekly email, from the root user, with the following content:
/etc/cron.weekly/update-notifier-common:
New release '16.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
How do I stop these emails, without upgrading to 16.04? Is there a method that doesn't involve disabling the script mentioned in the first line of the email?
Ideally I'd like to allow /etc/cron.weekly/update-notifier-common to continue to run, calling the /usr/lib/ubuntu-release-upgrader/release-upgrade-motd and /usr/lib/ubuntu-release-upgrader/check-new-release scripts, but stop new release messages. It would be useful for these scripts to still warn if my current release becomes EOL.
upgrade email notification
asked Oct 31 '16 at 9:35
ArronicalArronical
13.6k84993
I have an Ubuntu 14.04 server installation that consistently sends a weekly email, from the root user, with the following content:
/etc/cron.weekly/update-notifier-common:
New release '16.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
How do I stop these emails, without upgrading to 16.04? Is there a method that doesn't involve disabling the script mentioned in the first line of the email?
Ideally I'd like to allow /etc/cron.weekly/update-notifier-common to continue to run, calling the /usr/lib/ubuntu-release-upgrader/release-upgrade-motd and /usr/lib/ubuntu-release-upgrader/check-new-release scripts, but stop new release messages. It would be useful for these scripts to still warn if my current release becomes EOL.
upgrade email notification
upgrade email notification
asked Oct 31 '16 at 9:35
ArronicalArronical
13.6k84993
asked Oct 31 '16 at 9:35
ArronicalArronical
13.6k84993
edited Oct 31 '16 at 10:05
Arronical
asked Oct 31 '16 at 9:35
ArronicalArronical
13.6k84993
asked Oct 31 '16 at 9:35
ArronicalArronical
13.6k84993
asked Oct 31 '16 at 9:35
ArronicalArronical
13.6k84993
13.6k84993
It seems to check whether/usr/lib/ubuntu-release-upgrader/release-upgrade-motdexists and runs it if not.
– Arronical
Oct 31 '16 at 9:41
sorry yes I looked, and that runs/usr/lib/ubuntu-release-upgrader/check-new-releaseif there is a new release, and that is a python3 script that I am guessing is responsible for bothering you... but I have 16.10 so maybe it is not the same
– Zanna
Oct 31 '16 at 9:49
add a comment |
It seems to check whether/usr/lib/ubuntu-release-upgrader/release-upgrade-motdexists and runs it if not.
– Arronical
Oct 31 '16 at 9:41
sorry yes I looked, and that runs/usr/lib/ubuntu-release-upgrader/check-new-releaseif there is a new release, and that is a python3 script that I am guessing is responsible for bothering you... but I have 16.10 so maybe it is not the same
– Zanna
Oct 31 '16 at 9:49
It seems to check whether
/usr/lib/ubuntu-release-upgrader/release-upgrade-motd exists and runs it if not.– Arronical
Oct 31 '16 at 9:41
It seems to check whether
/usr/lib/ubuntu-release-upgrader/release-upgrade-motd exists and runs it if not.– Arronical
Oct 31 '16 at 9:41
sorry yes I looked, and that runs
/usr/lib/ubuntu-release-upgrader/check-new-release if there is a new release, and that is a python3 script that I am guessing is responsible for bothering you... but I have 16.10 so maybe it is not the same– Zanna
Oct 31 '16 at 9:49
sorry yes I looked, and that runs
/usr/lib/ubuntu-release-upgrader/check-new-release if there is a new release, and that is a python3 script that I am guessing is responsible for bothering you... but I have 16.10 so maybe it is not the same– Zanna
Oct 31 '16 at 9:49
add a comment |
2 Answers
2
active
oldest
votes
By default cron sends mail to the email address mentioned in the MAILTO environment variable on crontab, presumably you have set the email address, so any STDOUT/STDERR from any cron job will be sent to the email address.
The output is from /usr/lib/ubuntu-release-upgrader/release-upgrade-motd script (run by the weekly job /etc/cron.weekly/update-notifier-common) that checks for a new version, and dump the content of /var/lib/ubuntu-release-upgrader/release-upgrade-available file.
You have a few options:
Disable the job
Redirect STDOUT/STDERR from the script to
/dev/nullSet
MAILTO=""so that no mail will be sent. As/usr/sbin/anacronexists the script will be run byanacron, so setting this in/etc/anacrontabwould do too.
answered Oct 31 '16 at 9:55
heemaylheemayl
67.6k10142214
Thanks for the suggestions, definitely don't want to disable emails from cron entirely. Ideally I'd like to be able to ask it to stop telling me about new releases, but still do its other tasks, like warning when my version is out of support. Not sure that's possible though.
– Arronical
Oct 31 '16 at 10:02
@Arronical Thats what the script is doing.
– heemayl
Oct 31 '16 at 10:06
I understand that the script is responsible for that, but wondered if it's possible to stop the new release warning, while keeping the rest of the functionality.
– Arronical
Oct 31 '16 at 10:20
@Arronical It is (almost) the only thing it does, except running upgrading in the background.
– heemayl
Oct 31 '16 at 10:53
add a comment |
Since the /etc/update-motd.d/91-release-upgrade -script checks whether the following file is executable
/usr/lib/ubuntu-release-upgrader/release-upgrade-motd
a simple fix for this is to remove execute -flags from the file by running the following command
chmod a-x /usr/lib/ubuntu-release-upgrader/release-upgrade-motd
answered Feb 15 at 17:50
PHZ.fi-PharazonPHZ.fi-Pharazon
313
Will this produce an error message? If so that will generate an email that I'd like to avoid.
– Arronical
Feb 18 at 9:28
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%2f843778%2fhow-to-disable-release-upgrade-notification-emails%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
By default cron sends mail to the email address mentioned in the MAILTO environment variable on crontab, presumably you have set the email address, so any STDOUT/STDERR from any cron job will be sent to the email address.
The output is from /usr/lib/ubuntu-release-upgrader/release-upgrade-motd script (run by the weekly job /etc/cron.weekly/update-notifier-common) that checks for a new version, and dump the content of /var/lib/ubuntu-release-upgrader/release-upgrade-available file.
You have a few options:
Disable the job
Redirect STDOUT/STDERR from the script to
/dev/nullSet
MAILTO=""so that no mail will be sent. As/usr/sbin/anacronexists the script will be run byanacron, so setting this in/etc/anacrontabwould do too.
answered Oct 31 '16 at 9:55
heemaylheemayl
67.6k10142214
Thanks for the suggestions, definitely don't want to disable emails from cron entirely. Ideally I'd like to be able to ask it to stop telling me about new releases, but still do its other tasks, like warning when my version is out of support. Not sure that's possible though.
– Arronical
Oct 31 '16 at 10:02
@Arronical Thats what the script is doing.
– heemayl
Oct 31 '16 at 10:06
I understand that the script is responsible for that, but wondered if it's possible to stop the new release warning, while keeping the rest of the functionality.
– Arronical
Oct 31 '16 at 10:20
@Arronical It is (almost) the only thing it does, except running upgrading in the background.
– heemayl
Oct 31 '16 at 10:53
add a comment |
By default cron sends mail to the email address mentioned in the MAILTO environment variable on crontab, presumably you have set the email address, so any STDOUT/STDERR from any cron job will be sent to the email address.
The output is from /usr/lib/ubuntu-release-upgrader/release-upgrade-motd script (run by the weekly job /etc/cron.weekly/update-notifier-common) that checks for a new version, and dump the content of /var/lib/ubuntu-release-upgrader/release-upgrade-available file.
You have a few options:
Disable the job
Redirect STDOUT/STDERR from the script to
/dev/nullSet
MAILTO=""so that no mail will be sent. As/usr/sbin/anacronexists the script will be run byanacron, so setting this in/etc/anacrontabwould do too.
answered Oct 31 '16 at 9:55
heemaylheemayl
67.6k10142214
Thanks for the suggestions, definitely don't want to disable emails from cron entirely. Ideally I'd like to be able to ask it to stop telling me about new releases, but still do its other tasks, like warning when my version is out of support. Not sure that's possible though.
– Arronical
Oct 31 '16 at 10:02
@Arronical Thats what the script is doing.
– heemayl
Oct 31 '16 at 10:06
I understand that the script is responsible for that, but wondered if it's possible to stop the new release warning, while keeping the rest of the functionality.
– Arronical
Oct 31 '16 at 10:20
@Arronical It is (almost) the only thing it does, except running upgrading in the background.
– heemayl
Oct 31 '16 at 10:53
add a comment |
By default cron sends mail to the email address mentioned in the MAILTO environment variable on crontab, presumably you have set the email address, so any STDOUT/STDERR from any cron job will be sent to the email address.
The output is from /usr/lib/ubuntu-release-upgrader/release-upgrade-motd script (run by the weekly job /etc/cron.weekly/update-notifier-common) that checks for a new version, and dump the content of /var/lib/ubuntu-release-upgrader/release-upgrade-available file.
You have a few options:
Disable the job
Redirect STDOUT/STDERR from the script to
/dev/nullSet
MAILTO=""so that no mail will be sent. As/usr/sbin/anacronexists the script will be run byanacron, so setting this in/etc/anacrontabwould do too.
answered Oct 31 '16 at 9:55
heemaylheemayl
67.6k10142214
By default cron sends mail to the email address mentioned in the MAILTO environment variable on crontab, presumably you have set the email address, so any STDOUT/STDERR from any cron job will be sent to the email address.
The output is from /usr/lib/ubuntu-release-upgrader/release-upgrade-motd script (run by the weekly job /etc/cron.weekly/update-notifier-common) that checks for a new version, and dump the content of /var/lib/ubuntu-release-upgrader/release-upgrade-available file.
You have a few options:
Disable the job
Redirect STDOUT/STDERR from the script to
/dev/nullSet
MAILTO=""so that no mail will be sent. As/usr/sbin/anacronexists the script will be run byanacron, so setting this in/etc/anacrontabwould do too.
answered Oct 31 '16 at 9:55
heemaylheemayl
67.6k10142214
edited Oct 31 '16 at 10:01
answered Oct 31 '16 at 9:55
heemaylheemayl
67.6k10142214
answered Oct 31 '16 at 9:55
heemaylheemayl
67.6k10142214
answered Oct 31 '16 at 9:55
heemaylheemayl
67.6k10142214
67.6k10142214
Thanks for the suggestions, definitely don't want to disable emails from cron entirely. Ideally I'd like to be able to ask it to stop telling me about new releases, but still do its other tasks, like warning when my version is out of support. Not sure that's possible though.
– Arronical
Oct 31 '16 at 10:02
@Arronical Thats what the script is doing.
– heemayl
Oct 31 '16 at 10:06
I understand that the script is responsible for that, but wondered if it's possible to stop the new release warning, while keeping the rest of the functionality.
– Arronical
Oct 31 '16 at 10:20
@Arronical It is (almost) the only thing it does, except running upgrading in the background.
– heemayl
Oct 31 '16 at 10:53
add a comment |
Thanks for the suggestions, definitely don't want to disable emails from cron entirely. Ideally I'd like to be able to ask it to stop telling me about new releases, but still do its other tasks, like warning when my version is out of support. Not sure that's possible though.
– Arronical
Oct 31 '16 at 10:02
@Arronical Thats what the script is doing.
– heemayl
Oct 31 '16 at 10:06
I understand that the script is responsible for that, but wondered if it's possible to stop the new release warning, while keeping the rest of the functionality.
– Arronical
Oct 31 '16 at 10:20
@Arronical It is (almost) the only thing it does, except running upgrading in the background.
– heemayl
Oct 31 '16 at 10:53
Thanks for the suggestions, definitely don't want to disable emails from cron entirely. Ideally I'd like to be able to ask it to stop telling me about new releases, but still do its other tasks, like warning when my version is out of support. Not sure that's possible though.
– Arronical
Oct 31 '16 at 10:02
Thanks for the suggestions, definitely don't want to disable emails from cron entirely. Ideally I'd like to be able to ask it to stop telling me about new releases, but still do its other tasks, like warning when my version is out of support. Not sure that's possible though.
– Arronical
Oct 31 '16 at 10:02
@Arronical Thats what the script is doing.
– heemayl
Oct 31 '16 at 10:06
@Arronical Thats what the script is doing.
– heemayl
Oct 31 '16 at 10:06
I understand that the script is responsible for that, but wondered if it's possible to stop the new release warning, while keeping the rest of the functionality.
– Arronical
Oct 31 '16 at 10:20
I understand that the script is responsible for that, but wondered if it's possible to stop the new release warning, while keeping the rest of the functionality.
– Arronical
Oct 31 '16 at 10:20
@Arronical It is (almost) the only thing it does, except running upgrading in the background.
– heemayl
Oct 31 '16 at 10:53
@Arronical It is (almost) the only thing it does, except running upgrading in the background.
– heemayl
Oct 31 '16 at 10:53
add a comment |
Since the /etc/update-motd.d/91-release-upgrade -script checks whether the following file is executable
/usr/lib/ubuntu-release-upgrader/release-upgrade-motd
a simple fix for this is to remove execute -flags from the file by running the following command
chmod a-x /usr/lib/ubuntu-release-upgrader/release-upgrade-motd
answered Feb 15 at 17:50
PHZ.fi-PharazonPHZ.fi-Pharazon
313
Will this produce an error message? If so that will generate an email that I'd like to avoid.
– Arronical
Feb 18 at 9:28
add a comment |
Since the /etc/update-motd.d/91-release-upgrade -script checks whether the following file is executable
/usr/lib/ubuntu-release-upgrader/release-upgrade-motd
a simple fix for this is to remove execute -flags from the file by running the following command
chmod a-x /usr/lib/ubuntu-release-upgrader/release-upgrade-motd
answered Feb 15 at 17:50
PHZ.fi-PharazonPHZ.fi-Pharazon
313
Will this produce an error message? If so that will generate an email that I'd like to avoid.
– Arronical
Feb 18 at 9:28
add a comment |
Since the /etc/update-motd.d/91-release-upgrade -script checks whether the following file is executable
/usr/lib/ubuntu-release-upgrader/release-upgrade-motd
a simple fix for this is to remove execute -flags from the file by running the following command
chmod a-x /usr/lib/ubuntu-release-upgrader/release-upgrade-motd
answered Feb 15 at 17:50
PHZ.fi-PharazonPHZ.fi-Pharazon
313
Since the /etc/update-motd.d/91-release-upgrade -script checks whether the following file is executable
/usr/lib/ubuntu-release-upgrader/release-upgrade-motd
a simple fix for this is to remove execute -flags from the file by running the following command
chmod a-x /usr/lib/ubuntu-release-upgrader/release-upgrade-motd
answered Feb 15 at 17:50
PHZ.fi-PharazonPHZ.fi-Pharazon
313
answered Feb 15 at 17:50
PHZ.fi-PharazonPHZ.fi-Pharazon
313
answered Feb 15 at 17:50
PHZ.fi-PharazonPHZ.fi-Pharazon
313
answered Feb 15 at 17:50
PHZ.fi-PharazonPHZ.fi-Pharazon
313
313
Will this produce an error message? If so that will generate an email that I'd like to avoid.
– Arronical
Feb 18 at 9:28
add a comment |
Will this produce an error message? If so that will generate an email that I'd like to avoid.
– Arronical
Feb 18 at 9:28
Will this produce an error message? If so that will generate an email that I'd like to avoid.
– Arronical
Feb 18 at 9:28
Will this produce an error message? If so that will generate an email that I'd like to avoid.
– Arronical
Feb 18 at 9:28
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%2f843778%2fhow-to-disable-release-upgrade-notification-emails%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
It seems to check whether
/usr/lib/ubuntu-release-upgrader/release-upgrade-motdexists and runs it if not.– Arronical
Oct 31 '16 at 9:41
sorry yes I looked, and that runs
/usr/lib/ubuntu-release-upgrader/check-new-releaseif there is a new release, and that is a python3 script that I am guessing is responsible for bothering you... but I have 16.10 so maybe it is not the same– Zanna
Oct 31 '16 at 9:49