update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
I have recently installed snmpd on my Ubuntu 16.04 VM. I was trying out few things and at some point I wanted to restart the application using
service snmpd restart
It did not work, giving the message undefined symbol: smux_listen_sd
I serched the internet for a possible reasons, but the main solution I was given was that there is another installed version that I need to remove. I looked for previous versions, there was nothing.
So after couple of uninstallations and re installations, it now works.
However, at the end of the installation, I noticed the message:
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: stop runlevel arguments (1) do not match snmpd Default-Stop values (0 1 6)
Does that mean I can no longer use service ... start
or systemctl ... start
?
If so, how should I start and stop an app?
systemd services
add a comment |
I have recently installed snmpd on my Ubuntu 16.04 VM. I was trying out few things and at some point I wanted to restart the application using
service snmpd restart
It did not work, giving the message undefined symbol: smux_listen_sd
I serched the internet for a possible reasons, but the main solution I was given was that there is another installed version that I need to remove. I looked for previous versions, there was nothing.
So after couple of uninstallations and re installations, it now works.
However, at the end of the installation, I noticed the message:
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: stop runlevel arguments (1) do not match snmpd Default-Stop values (0 1 6)
Does that mean I can no longer use service ... start
or systemctl ... start
?
If so, how should I start and stop an app?
systemd services
add a comment |
I have recently installed snmpd on my Ubuntu 16.04 VM. I was trying out few things and at some point I wanted to restart the application using
service snmpd restart
It did not work, giving the message undefined symbol: smux_listen_sd
I serched the internet for a possible reasons, but the main solution I was given was that there is another installed version that I need to remove. I looked for previous versions, there was nothing.
So after couple of uninstallations and re installations, it now works.
However, at the end of the installation, I noticed the message:
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: stop runlevel arguments (1) do not match snmpd Default-Stop values (0 1 6)
Does that mean I can no longer use service ... start
or systemctl ... start
?
If so, how should I start and stop an app?
systemd services
I have recently installed snmpd on my Ubuntu 16.04 VM. I was trying out few things and at some point I wanted to restart the application using
service snmpd restart
It did not work, giving the message undefined symbol: smux_listen_sd
I serched the internet for a possible reasons, but the main solution I was given was that there is another installed version that I need to remove. I looked for previous versions, there was nothing.
So after couple of uninstallations and re installations, it now works.
However, at the end of the installation, I noticed the message:
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: stop runlevel arguments (1) do not match snmpd Default-Stop values (0 1 6)
Does that mean I can no longer use service ... start
or systemctl ... start
?
If so, how should I start and stop an app?
systemd services
systemd services
asked Nov 7 '18 at 10:44
PhoenixBluePhoenixBlue
1011
1011
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The "start" and "stop" arguments are deprecated!
Roger Leigh (Debian developer team) announced that in debian-devel, on May 2013:
the options still exist, but they
just invoke the "defaults" action.
As you can see in an extract of update-rc.d(8) manpage:
The correct way to disable services is to configure the service as stopped in all runlevels in which it is started by default.
New contributor
I noticed they still exists (the options) but they only produce an error when I'm using them with the snmp service... I've searched for quite some time, did not find an answer to that. Giving me headaches...
– PhoenixBlue
Jan 17 at 14:41
update-rc.d install and remove System-V style init script links into the boot sequence.. You can still use it with defaults and remove options but it is still for the boot sequence! systemctl start / stop is not in boot sequence..
– lunix15
Jan 17 at 15:03
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%2f1090772%2fupdate-rc-d-warning-start-and-stop-actions-are-no-longer-supported-falling-ba%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The "start" and "stop" arguments are deprecated!
Roger Leigh (Debian developer team) announced that in debian-devel, on May 2013:
the options still exist, but they
just invoke the "defaults" action.
As you can see in an extract of update-rc.d(8) manpage:
The correct way to disable services is to configure the service as stopped in all runlevels in which it is started by default.
New contributor
I noticed they still exists (the options) but they only produce an error when I'm using them with the snmp service... I've searched for quite some time, did not find an answer to that. Giving me headaches...
– PhoenixBlue
Jan 17 at 14:41
update-rc.d install and remove System-V style init script links into the boot sequence.. You can still use it with defaults and remove options but it is still for the boot sequence! systemctl start / stop is not in boot sequence..
– lunix15
Jan 17 at 15:03
add a comment |
The "start" and "stop" arguments are deprecated!
Roger Leigh (Debian developer team) announced that in debian-devel, on May 2013:
the options still exist, but they
just invoke the "defaults" action.
As you can see in an extract of update-rc.d(8) manpage:
The correct way to disable services is to configure the service as stopped in all runlevels in which it is started by default.
New contributor
I noticed they still exists (the options) but they only produce an error when I'm using them with the snmp service... I've searched for quite some time, did not find an answer to that. Giving me headaches...
– PhoenixBlue
Jan 17 at 14:41
update-rc.d install and remove System-V style init script links into the boot sequence.. You can still use it with defaults and remove options but it is still for the boot sequence! systemctl start / stop is not in boot sequence..
– lunix15
Jan 17 at 15:03
add a comment |
The "start" and "stop" arguments are deprecated!
Roger Leigh (Debian developer team) announced that in debian-devel, on May 2013:
the options still exist, but they
just invoke the "defaults" action.
As you can see in an extract of update-rc.d(8) manpage:
The correct way to disable services is to configure the service as stopped in all runlevels in which it is started by default.
New contributor
The "start" and "stop" arguments are deprecated!
Roger Leigh (Debian developer team) announced that in debian-devel, on May 2013:
the options still exist, but they
just invoke the "defaults" action.
As you can see in an extract of update-rc.d(8) manpage:
The correct way to disable services is to configure the service as stopped in all runlevels in which it is started by default.
New contributor
New contributor
answered Jan 17 at 14:37
lunix15lunix15
11
11
New contributor
New contributor
I noticed they still exists (the options) but they only produce an error when I'm using them with the snmp service... I've searched for quite some time, did not find an answer to that. Giving me headaches...
– PhoenixBlue
Jan 17 at 14:41
update-rc.d install and remove System-V style init script links into the boot sequence.. You can still use it with defaults and remove options but it is still for the boot sequence! systemctl start / stop is not in boot sequence..
– lunix15
Jan 17 at 15:03
add a comment |
I noticed they still exists (the options) but they only produce an error when I'm using them with the snmp service... I've searched for quite some time, did not find an answer to that. Giving me headaches...
– PhoenixBlue
Jan 17 at 14:41
update-rc.d install and remove System-V style init script links into the boot sequence.. You can still use it with defaults and remove options but it is still for the boot sequence! systemctl start / stop is not in boot sequence..
– lunix15
Jan 17 at 15:03
I noticed they still exists (the options) but they only produce an error when I'm using them with the snmp service... I've searched for quite some time, did not find an answer to that. Giving me headaches...
– PhoenixBlue
Jan 17 at 14:41
I noticed they still exists (the options) but they only produce an error when I'm using them with the snmp service... I've searched for quite some time, did not find an answer to that. Giving me headaches...
– PhoenixBlue
Jan 17 at 14:41
update-rc.d install and remove System-V style init script links into the boot sequence.. You can still use it with defaults and remove options but it is still for the boot sequence! systemctl start / stop is not in boot sequence..
– lunix15
Jan 17 at 15:03
update-rc.d install and remove System-V style init script links into the boot sequence.. You can still use it with defaults and remove options but it is still for the boot sequence! systemctl start / stop is not in boot sequence..
– lunix15
Jan 17 at 15:03
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%2f1090772%2fupdate-rc-d-warning-start-and-stop-actions-are-no-longer-supported-falling-ba%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