How to add service to run at boot on slackware linux?
I am trying a Slackware 14.2. I can start sshd by /etc/rc.d/rc.inet1 sshd start but my question is how to add service to run at boot on slackware linux? Basically how to permanently add services to system on Slackware Linux and also check that service status. So far I am able to achieve the above using this link,
$ sudo nano /etc/rc.d/rc.M
and adding these lines
# Start the sshd server
if [ -x /etc/rc.d/rc.sshd ]; then
. /etc/rc.d/rc.sshd
fi
and it did work and ssh server started automatically after boot as I was able to ssh to that system but how to check that service status within the system other than ps aux | grep ssh or netstat -lntp | grep ssh or using tools like lsof? What I meant is some thing usual way like sudo service sshd status or sudo systemctl status sshd .
services slackware autostart
asked May 29 '18 at 20:31
Pavel SayekatPavel Sayekat
198111
add a comment |
I am trying a Slackware 14.2. I can start sshd by /etc/rc.d/rc.inet1 sshd start but my question is how to add service to run at boot on slackware linux? Basically how to permanently add services to system on Slackware Linux and also check that service status. So far I am able to achieve the above using this link,
$ sudo nano /etc/rc.d/rc.M
and adding these lines
# Start the sshd server
if [ -x /etc/rc.d/rc.sshd ]; then
. /etc/rc.d/rc.sshd
fi
and it did work and ssh server started automatically after boot as I was able to ssh to that system but how to check that service status within the system other than ps aux | grep ssh or netstat -lntp | grep ssh or using tools like lsof? What I meant is some thing usual way like sudo service sshd status or sudo systemctl status sshd .
services slackware autostart
asked May 29 '18 at 20:31
Pavel SayekatPavel Sayekat
198111
Oops! I should have known that systemd and openrc/init walks through their separate paths.
– Pavel Sayekat
Dec 28 '18 at 16:27
add a comment |
I am trying a Slackware 14.2. I can start sshd by /etc/rc.d/rc.inet1 sshd start but my question is how to add service to run at boot on slackware linux? Basically how to permanently add services to system on Slackware Linux and also check that service status. So far I am able to achieve the above using this link,
$ sudo nano /etc/rc.d/rc.M
and adding these lines
# Start the sshd server
if [ -x /etc/rc.d/rc.sshd ]; then
. /etc/rc.d/rc.sshd
fi
and it did work and ssh server started automatically after boot as I was able to ssh to that system but how to check that service status within the system other than ps aux | grep ssh or netstat -lntp | grep ssh or using tools like lsof? What I meant is some thing usual way like sudo service sshd status or sudo systemctl status sshd .
services slackware autostart
asked May 29 '18 at 20:31
Pavel SayekatPavel Sayekat
198111
I am trying a Slackware 14.2. I can start sshd by /etc/rc.d/rc.inet1 sshd start but my question is how to add service to run at boot on slackware linux? Basically how to permanently add services to system on Slackware Linux and also check that service status. So far I am able to achieve the above using this link,
$ sudo nano /etc/rc.d/rc.M
and adding these lines
# Start the sshd server
if [ -x /etc/rc.d/rc.sshd ]; then
. /etc/rc.d/rc.sshd
fi
and it did work and ssh server started automatically after boot as I was able to ssh to that system but how to check that service status within the system other than ps aux | grep ssh or netstat -lntp | grep ssh or using tools like lsof? What I meant is some thing usual way like sudo service sshd status or sudo systemctl status sshd .
services slackware autostart
services slackware autostart
asked May 29 '18 at 20:31
Pavel SayekatPavel Sayekat
198111
asked May 29 '18 at 20:31
Pavel SayekatPavel Sayekat
198111
edited Dec 28 '18 at 16:25
Pavel Sayekat
asked May 29 '18 at 20:31
Pavel SayekatPavel Sayekat
198111
asked May 29 '18 at 20:31
Pavel SayekatPavel Sayekat
198111
asked May 29 '18 at 20:31
Pavel SayekatPavel Sayekat
198111
198111
Oops! I should have known that systemd and openrc/init walks through their separate paths.
– Pavel Sayekat
Dec 28 '18 at 16:27
add a comment |
Oops! I should have known that systemd and openrc/init walks through their separate paths.
– Pavel Sayekat
Dec 28 '18 at 16:27
Oops! I should have known that systemd and openrc/init walks through their separate paths.
– Pavel Sayekat
Dec 28 '18 at 16:27
Oops! I should have known that systemd and openrc/init walks through their separate paths.
– Pavel Sayekat
Dec 28 '18 at 16:27
add a comment |
2 Answers
2
active
oldest
votes
Any services or daemons that use the network should be started from
[/etc/rc.d/rc.inet2]. Most of the rc scripts in charge of starting daemons like inetd, sshd, bind, nfs, etc get called fromrc.inet2. - Source http://www.slackware.com/config/network.php
answered May 29 '18 at 20:53
Emmanuel RosaEmmanuel Rosa
3,0551612
add a comment |
Slackware use the BSD-style init system. sshd daemon is handled on boot with rc.inet2 script and is handled on shutdown with rc.0 and rc.6 on reboot.
To start sshd daemon on boot add execute permission to rc.sshd script:
chmod +x /etc/rc.d/rc.sshd
To disable sshd on boot remove execute permission:
chmod -x /etc/rc.d/rc.sshd
In alternative you can manage sshd daemon (stop&start and restart) using the rc script:
sh /etc/rc.d/rc.sshd
usage /etc/rc.d/rc.sshd start|stop|restart
answered Jan 4 at 22:43
Giuseppe Di TerlizziGiuseppe Di Terlizzi
11
New contributor
Giuseppe Di Terlizzi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f446789%2fhow-to-add-service-to-run-at-boot-on-slackware-linux%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
Any services or daemons that use the network should be started from
[/etc/rc.d/rc.inet2]. Most of the rc scripts in charge of starting daemons like inetd, sshd, bind, nfs, etc get called fromrc.inet2. - Source http://www.slackware.com/config/network.php
answered May 29 '18 at 20:53
Emmanuel RosaEmmanuel Rosa
3,0551612
add a comment |
Any services or daemons that use the network should be started from
[/etc/rc.d/rc.inet2]. Most of the rc scripts in charge of starting daemons like inetd, sshd, bind, nfs, etc get called fromrc.inet2. - Source http://www.slackware.com/config/network.php
answered May 29 '18 at 20:53
Emmanuel RosaEmmanuel Rosa
3,0551612
add a comment |
Any services or daemons that use the network should be started from
[/etc/rc.d/rc.inet2]. Most of the rc scripts in charge of starting daemons like inetd, sshd, bind, nfs, etc get called fromrc.inet2. - Source http://www.slackware.com/config/network.php
answered May 29 '18 at 20:53
Emmanuel RosaEmmanuel Rosa
3,0551612
Any services or daemons that use the network should be started from
[/etc/rc.d/rc.inet2]. Most of the rc scripts in charge of starting daemons like inetd, sshd, bind, nfs, etc get called fromrc.inet2. - Source http://www.slackware.com/config/network.php
answered May 29 '18 at 20:53
Emmanuel RosaEmmanuel Rosa
3,0551612
answered May 29 '18 at 20:53
Emmanuel RosaEmmanuel Rosa
3,0551612
answered May 29 '18 at 20:53
Emmanuel RosaEmmanuel Rosa
3,0551612
answered May 29 '18 at 20:53
Emmanuel RosaEmmanuel Rosa
3,0551612
3,0551612
add a comment |
add a comment |
Slackware use the BSD-style init system. sshd daemon is handled on boot with rc.inet2 script and is handled on shutdown with rc.0 and rc.6 on reboot.
To start sshd daemon on boot add execute permission to rc.sshd script:
chmod +x /etc/rc.d/rc.sshd
To disable sshd on boot remove execute permission:
chmod -x /etc/rc.d/rc.sshd
In alternative you can manage sshd daemon (stop&start and restart) using the rc script:
sh /etc/rc.d/rc.sshd
usage /etc/rc.d/rc.sshd start|stop|restart
answered Jan 4 at 22:43
Giuseppe Di TerlizziGiuseppe Di Terlizzi
11
New contributor
Giuseppe Di Terlizzi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Slackware use the BSD-style init system. sshd daemon is handled on boot with rc.inet2 script and is handled on shutdown with rc.0 and rc.6 on reboot.
To start sshd daemon on boot add execute permission to rc.sshd script:
chmod +x /etc/rc.d/rc.sshd
To disable sshd on boot remove execute permission:
chmod -x /etc/rc.d/rc.sshd
In alternative you can manage sshd daemon (stop&start and restart) using the rc script:
sh /etc/rc.d/rc.sshd
usage /etc/rc.d/rc.sshd start|stop|restart
answered Jan 4 at 22:43
Giuseppe Di TerlizziGiuseppe Di Terlizzi
11
New contributor
Giuseppe Di Terlizzi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Slackware use the BSD-style init system. sshd daemon is handled on boot with rc.inet2 script and is handled on shutdown with rc.0 and rc.6 on reboot.
To start sshd daemon on boot add execute permission to rc.sshd script:
chmod +x /etc/rc.d/rc.sshd
To disable sshd on boot remove execute permission:
chmod -x /etc/rc.d/rc.sshd
In alternative you can manage sshd daemon (stop&start and restart) using the rc script:
sh /etc/rc.d/rc.sshd
usage /etc/rc.d/rc.sshd start|stop|restart
answered Jan 4 at 22:43
Giuseppe Di TerlizziGiuseppe Di Terlizzi
11
New contributor
Giuseppe Di Terlizzi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Slackware use the BSD-style init system. sshd daemon is handled on boot with rc.inet2 script and is handled on shutdown with rc.0 and rc.6 on reboot.
To start sshd daemon on boot add execute permission to rc.sshd script:
chmod +x /etc/rc.d/rc.sshd
To disable sshd on boot remove execute permission:
chmod -x /etc/rc.d/rc.sshd
In alternative you can manage sshd daemon (stop&start and restart) using the rc script:
sh /etc/rc.d/rc.sshd
usage /etc/rc.d/rc.sshd start|stop|restart
answered Jan 4 at 22:43
Giuseppe Di TerlizziGiuseppe Di Terlizzi
11
New contributor
Giuseppe Di Terlizzi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Jan 4 at 22:43
Giuseppe Di TerlizziGiuseppe Di Terlizzi
11
New contributor
Giuseppe Di Terlizzi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Jan 4 at 22:43
Giuseppe Di TerlizziGiuseppe Di Terlizzi
11
answered Jan 4 at 22:43
Giuseppe Di TerlizziGiuseppe Di Terlizzi
11
11
New contributor
Giuseppe Di Terlizzi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Giuseppe Di Terlizzi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Giuseppe Di Terlizzi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f446789%2fhow-to-add-service-to-run-at-boot-on-slackware-linux%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
Oops! I should have known that systemd and openrc/init walks through their separate paths.
– Pavel Sayekat
Dec 28 '18 at 16:27