Run rcp.statd without systemd (Ubuntu on Windows Subsystem for Linux (WSL))

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












When I run certain mount commands, I am told



mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.


The command I find online to start statd is:



systemctl start statd


which gives anothe error:



> systemctl start statd
Failed to add /run/systemd/ask-password to directory watch: No such file or directory
Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
Failed to connect to bus: No such file or directory


Other sources make it clear that there is no systemd on Ubuntu WSL.



How can I start statd without systemd?










share|improve this question

























    up vote
    0
    down vote

    favorite












    When I run certain mount commands, I am told



    mount.nfs: rpc.statd is not running but is required for remote locking.
    mount.nfs: Either use '-o nolock' to keep locks local, or start statd.


    The command I find online to start statd is:



    systemctl start statd


    which gives anothe error:



    > systemctl start statd
    Failed to add /run/systemd/ask-password to directory watch: No such file or directory
    Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
    Failed to connect to bus: No such file or directory


    Other sources make it clear that there is no systemd on Ubuntu WSL.



    How can I start statd without systemd?










    share|improve this question























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      When I run certain mount commands, I am told



      mount.nfs: rpc.statd is not running but is required for remote locking.
      mount.nfs: Either use '-o nolock' to keep locks local, or start statd.


      The command I find online to start statd is:



      systemctl start statd


      which gives anothe error:



      > systemctl start statd
      Failed to add /run/systemd/ask-password to directory watch: No such file or directory
      Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
      Failed to connect to bus: No such file or directory


      Other sources make it clear that there is no systemd on Ubuntu WSL.



      How can I start statd without systemd?










      share|improve this question













      When I run certain mount commands, I am told



      mount.nfs: rpc.statd is not running but is required for remote locking.
      mount.nfs: Either use '-o nolock' to keep locks local, or start statd.


      The command I find online to start statd is:



      systemctl start statd


      which gives anothe error:



      > systemctl start statd
      Failed to add /run/systemd/ask-password to directory watch: No such file or directory
      Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
      Failed to connect to bus: No such file or directory


      Other sources make it clear that there is no systemd on Ubuntu WSL.



      How can I start statd without systemd?







      systemd windows-subsystem-for-linux






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 17 at 21:55









      jtpereyda

      8582916




      8582916




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          systemd ultimately just run binaries. So without systemd, you can the binaries directly.



          If you need the binary to run the background. you can run it nohup.



          If you need the process to be managed then you'll need another tool that can do things like start it on boot and automatically restart it if fails.






          share|improve this answer




















            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',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025947%2frun-rcp-statd-without-systemd-ubuntu-on-windows-subsystem-for-linux-wsl%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            systemd ultimately just run binaries. So without systemd, you can the binaries directly.



            If you need the binary to run the background. you can run it nohup.



            If you need the process to be managed then you'll need another tool that can do things like start it on boot and automatically restart it if fails.






            share|improve this answer
























              up vote
              0
              down vote













              systemd ultimately just run binaries. So without systemd, you can the binaries directly.



              If you need the binary to run the background. you can run it nohup.



              If you need the process to be managed then you'll need another tool that can do things like start it on boot and automatically restart it if fails.






              share|improve this answer






















                up vote
                0
                down vote










                up vote
                0
                down vote









                systemd ultimately just run binaries. So without systemd, you can the binaries directly.



                If you need the binary to run the background. you can run it nohup.



                If you need the process to be managed then you'll need another tool that can do things like start it on boot and automatically restart it if fails.






                share|improve this answer












                systemd ultimately just run binaries. So without systemd, you can the binaries directly.



                If you need the binary to run the background. you can run it nohup.



                If you need the process to be managed then you'll need another tool that can do things like start it on boot and automatically restart it if fails.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Apr 19 at 18:25









                Mark Stosberg

                2,10411523




                2,10411523



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025947%2frun-rcp-statd-without-systemd-ubuntu-on-windows-subsystem-for-linux-wsl%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    pylint3 and pip3 broken

                    Missing snmpget and snmpwalk

                    How to enroll fingerprints to Ubuntu 17.10 with VFS491