How to add service to run at boot on slackware linux?












0














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 .










share|improve this question
























  • Oops! I should have known that systemd and openrc/init walks through their separate paths.
    – Pavel Sayekat
    1 hour ago


















0














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 .










share|improve this question
























  • Oops! I should have known that systemd and openrc/init walks through their separate paths.
    – Pavel Sayekat
    1 hour ago
















0












0








0







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 .










share|improve this question















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 1 hour ago

























asked May 29 at 20:31









Pavel Sayekat

198111




198111












  • Oops! I should have known that systemd and openrc/init walks through their separate paths.
    – Pavel Sayekat
    1 hour ago




















  • Oops! I should have known that systemd and openrc/init walks through their separate paths.
    – Pavel Sayekat
    1 hour ago


















Oops! I should have known that systemd and openrc/init walks through their separate paths.
– Pavel Sayekat
1 hour ago






Oops! I should have known that systemd and openrc/init walks through their separate paths.
– Pavel Sayekat
1 hour ago












1 Answer
1






active

oldest

votes


















1















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 from rc.inet2. - Source http://www.slackware.com/config/network.php







share|improve this answer





















    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
    });


    }
    });














    draft saved

    draft discarded


















    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

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1















    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 from rc.inet2. - Source http://www.slackware.com/config/network.php







    share|improve this answer


























      1















      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 from rc.inet2. - Source http://www.slackware.com/config/network.php







      share|improve this answer
























        1












        1








        1







        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 from rc.inet2. - Source http://www.slackware.com/config/network.php







        share|improve this answer













        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 from rc.inet2. - Source http://www.slackware.com/config/network.php








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 29 at 20:53









        Emmanuel Rosa

        2,9801612




        2,9801612






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            Accessing regular linux commands in Huawei's Dopra Linux

            Can't connect RFCOMM socket: Host is down

            Kernel panic - not syncing: Fatal Exception in Interrupt