Make systemd stop starting unwanted wpa_supplicant service?Systemd Service Script Not EchoingI can't enable...

Multi tool use
Multi tool use

Can you use one creature for both convoke and delve for Hogaak?

What does this Swiss black on yellow rectangular traffic sign with a symbol looking like a dart mean?

What are the pros and cons for the two possible "gear directions" when parking the car on a hill?

Encounter design and XP thresholds

Justifying Affordable Bespoke Spaceships

How can I prevent a user from copying files on another hard drive?

Why isn't my calculation that we should be able to see the sun well beyond the observable universe valid?

What triggered jesuits' ban on infinitesimals in 1632?

How did Gollum enter Moria?

A word for delight at someone else's failure?

How much steel armor can you wear and still be able to swim?

Is the continuity test limit resistance of a multimeter standard?

How did the Vostok ejection seat safely eject an astronaut from a sealed space capsule?

Prisoner on alien planet escapes by making up a story about ghost companions and wins the war

Is there official documentation on directories like ~/.config and ~/.cache?

Fantaisie Impromptu - Specific fingering issue

Is it illegal to withhold someone's passport and green card in California?

Definition of 'vrit'

Why does independence imply zero correlation?

What does it cost to buy a tavern?

What happened to Hopper's girlfriend in season one?

What constitutes a syllable?

What is the most suitable position for a bishop here?

Boss wants someone else to lead a project based on the idea I presented to him



Make systemd stop starting unwanted wpa_supplicant service?


Systemd Service Script Not EchoingI can't enable or disable a user service: Failed to execute operation: No such file or directorymysql service restarted during user being connected lead to failing servicestart a service a at bootime in systemdsystemd: How to unmask a service whose unit file is empty?Why x0vncserver is not starting at boot?What is the difference between Process: and Main PID: in the output of systemctl status?Why is systemd stopping service immediately after it is started?Daemon not started by systemdsystemd not autorestarting the last docker container after it crashes or kill -9 or docker stop service






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







9















I wanted to disable systemd unwanted attempts to automatically start wpa_supplicant. I thougth I could simply run a



sudo systemctl disable wpa_supplicant.service --global


and I would not be seeing a wpa_supplicant in ps -ef output anymore. Anyway this did not work.
How can I make it work?



My problem at hand might be best descriped by the output of



$>systemctl status wpa_supplicant*
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: disabled)
Active: active (running) since Sun 2016-08-28 20:57:37 CEST; 14min ago


where as you can see the disabled service is anyway loaded and active, thanks to systemd completely helping me do the simpletest thing ;)



Update

I seem to have had some luck by brutely removing those files:



wpa_supplicant-nl80211@.service
wpa_supplicant.service
wpa_supplicant@.service
wpa_supplicant-wired@.service


from /usr/lib/systemd/system folder. Guess what? after restart wpa is finally not started by systemd anymore. It strikes me though there must have been a more peaceful / conciliatory way to get systemd to have the system not being started.










share|improve this question

























  • Did masking the unit do nothing for you?

    – Kalvin Lee
    Aug 28 '16 at 20:26











  • @KalvinLee I am not sure if what I did (removing the files) and masking (to my undestanding that would be keeping links named as those files which point to /dev/null is not essentually much of the same thing.) What you suggest is something I try. I must have not been looking enough in unix.se to see that disbale vs mask systemd question. I will try and state back soon, to update the question

    – humanityANDpeace
    Aug 28 '16 at 21:17











  • Did disabling the template (wpa_supplicant@.service) help?

    – maxf
    Aug 29 '16 at 7:54






  • 1





    @maxf yes (see that in the update I did remove also the template file) and that worked. I guess the real answer here was that what Kalvin Lee suggessted namely that really disabeling (not get it to start , even as a dependence or else, is to mask it). systemctl mask is the real disable (meaning the service is not there later on).

    – humanityANDpeace
    Aug 29 '16 at 9:05


















9















I wanted to disable systemd unwanted attempts to automatically start wpa_supplicant. I thougth I could simply run a



sudo systemctl disable wpa_supplicant.service --global


and I would not be seeing a wpa_supplicant in ps -ef output anymore. Anyway this did not work.
How can I make it work?



My problem at hand might be best descriped by the output of



$>systemctl status wpa_supplicant*
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: disabled)
Active: active (running) since Sun 2016-08-28 20:57:37 CEST; 14min ago


where as you can see the disabled service is anyway loaded and active, thanks to systemd completely helping me do the simpletest thing ;)



Update

I seem to have had some luck by brutely removing those files:



wpa_supplicant-nl80211@.service
wpa_supplicant.service
wpa_supplicant@.service
wpa_supplicant-wired@.service


from /usr/lib/systemd/system folder. Guess what? after restart wpa is finally not started by systemd anymore. It strikes me though there must have been a more peaceful / conciliatory way to get systemd to have the system not being started.










share|improve this question

























  • Did masking the unit do nothing for you?

    – Kalvin Lee
    Aug 28 '16 at 20:26











  • @KalvinLee I am not sure if what I did (removing the files) and masking (to my undestanding that would be keeping links named as those files which point to /dev/null is not essentually much of the same thing.) What you suggest is something I try. I must have not been looking enough in unix.se to see that disbale vs mask systemd question. I will try and state back soon, to update the question

    – humanityANDpeace
    Aug 28 '16 at 21:17











  • Did disabling the template (wpa_supplicant@.service) help?

    – maxf
    Aug 29 '16 at 7:54






  • 1





    @maxf yes (see that in the update I did remove also the template file) and that worked. I guess the real answer here was that what Kalvin Lee suggessted namely that really disabeling (not get it to start , even as a dependence or else, is to mask it). systemctl mask is the real disable (meaning the service is not there later on).

    – humanityANDpeace
    Aug 29 '16 at 9:05














9












9








9








I wanted to disable systemd unwanted attempts to automatically start wpa_supplicant. I thougth I could simply run a



sudo systemctl disable wpa_supplicant.service --global


and I would not be seeing a wpa_supplicant in ps -ef output anymore. Anyway this did not work.
How can I make it work?



My problem at hand might be best descriped by the output of



$>systemctl status wpa_supplicant*
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: disabled)
Active: active (running) since Sun 2016-08-28 20:57:37 CEST; 14min ago


where as you can see the disabled service is anyway loaded and active, thanks to systemd completely helping me do the simpletest thing ;)



Update

I seem to have had some luck by brutely removing those files:



wpa_supplicant-nl80211@.service
wpa_supplicant.service
wpa_supplicant@.service
wpa_supplicant-wired@.service


from /usr/lib/systemd/system folder. Guess what? after restart wpa is finally not started by systemd anymore. It strikes me though there must have been a more peaceful / conciliatory way to get systemd to have the system not being started.










share|improve this question
















I wanted to disable systemd unwanted attempts to automatically start wpa_supplicant. I thougth I could simply run a



sudo systemctl disable wpa_supplicant.service --global


and I would not be seeing a wpa_supplicant in ps -ef output anymore. Anyway this did not work.
How can I make it work?



My problem at hand might be best descriped by the output of



$>systemctl status wpa_supplicant*
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: disabled)
Active: active (running) since Sun 2016-08-28 20:57:37 CEST; 14min ago


where as you can see the disabled service is anyway loaded and active, thanks to systemd completely helping me do the simpletest thing ;)



Update

I seem to have had some luck by brutely removing those files:



wpa_supplicant-nl80211@.service
wpa_supplicant.service
wpa_supplicant@.service
wpa_supplicant-wired@.service


from /usr/lib/systemd/system folder. Guess what? after restart wpa is finally not started by systemd anymore. It strikes me though there must have been a more peaceful / conciliatory way to get systemd to have the system not being started.







systemd configuration wpa-supplicant






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 30 '16 at 22:02









GAD3R

29.3k1960118




29.3k1960118










asked Aug 28 '16 at 19:22









humanityANDpeacehumanityANDpeace

5,44553659




5,44553659













  • Did masking the unit do nothing for you?

    – Kalvin Lee
    Aug 28 '16 at 20:26











  • @KalvinLee I am not sure if what I did (removing the files) and masking (to my undestanding that would be keeping links named as those files which point to /dev/null is not essentually much of the same thing.) What you suggest is something I try. I must have not been looking enough in unix.se to see that disbale vs mask systemd question. I will try and state back soon, to update the question

    – humanityANDpeace
    Aug 28 '16 at 21:17











  • Did disabling the template (wpa_supplicant@.service) help?

    – maxf
    Aug 29 '16 at 7:54






  • 1





    @maxf yes (see that in the update I did remove also the template file) and that worked. I guess the real answer here was that what Kalvin Lee suggessted namely that really disabeling (not get it to start , even as a dependence or else, is to mask it). systemctl mask is the real disable (meaning the service is not there later on).

    – humanityANDpeace
    Aug 29 '16 at 9:05



















  • Did masking the unit do nothing for you?

    – Kalvin Lee
    Aug 28 '16 at 20:26











  • @KalvinLee I am not sure if what I did (removing the files) and masking (to my undestanding that would be keeping links named as those files which point to /dev/null is not essentually much of the same thing.) What you suggest is something I try. I must have not been looking enough in unix.se to see that disbale vs mask systemd question. I will try and state back soon, to update the question

    – humanityANDpeace
    Aug 28 '16 at 21:17











  • Did disabling the template (wpa_supplicant@.service) help?

    – maxf
    Aug 29 '16 at 7:54






  • 1





    @maxf yes (see that in the update I did remove also the template file) and that worked. I guess the real answer here was that what Kalvin Lee suggessted namely that really disabeling (not get it to start , even as a dependence or else, is to mask it). systemctl mask is the real disable (meaning the service is not there later on).

    – humanityANDpeace
    Aug 29 '16 at 9:05

















Did masking the unit do nothing for you?

– Kalvin Lee
Aug 28 '16 at 20:26





Did masking the unit do nothing for you?

– Kalvin Lee
Aug 28 '16 at 20:26













@KalvinLee I am not sure if what I did (removing the files) and masking (to my undestanding that would be keeping links named as those files which point to /dev/null is not essentually much of the same thing.) What you suggest is something I try. I must have not been looking enough in unix.se to see that disbale vs mask systemd question. I will try and state back soon, to update the question

– humanityANDpeace
Aug 28 '16 at 21:17





@KalvinLee I am not sure if what I did (removing the files) and masking (to my undestanding that would be keeping links named as those files which point to /dev/null is not essentually much of the same thing.) What you suggest is something I try. I must have not been looking enough in unix.se to see that disbale vs mask systemd question. I will try and state back soon, to update the question

– humanityANDpeace
Aug 28 '16 at 21:17













Did disabling the template (wpa_supplicant@.service) help?

– maxf
Aug 29 '16 at 7:54





Did disabling the template (wpa_supplicant@.service) help?

– maxf
Aug 29 '16 at 7:54




1




1





@maxf yes (see that in the update I did remove also the template file) and that worked. I guess the real answer here was that what Kalvin Lee suggessted namely that really disabeling (not get it to start , even as a dependence or else, is to mask it). systemctl mask is the real disable (meaning the service is not there later on).

– humanityANDpeace
Aug 29 '16 at 9:05





@maxf yes (see that in the update I did remove also the template file) and that worked. I guess the real answer here was that what Kalvin Lee suggessted namely that really disabeling (not get it to start , even as a dependence or else, is to mask it). systemctl mask is the real disable (meaning the service is not there later on).

– humanityANDpeace
Aug 29 '16 at 9:05










3 Answers
3






active

oldest

votes


















4














I ran into the same issue as yours. After some digging, I found a folder called:



/usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service


This is file is used to allow the service to be activated by d-bus. d-bus can activate the service even if it is disabled. I confirmed that this was happening by re-naming the file, and then rebooting. I saw that at this point wpa_supplicant had not been started! To chase the issue down further would required finding out what program is activating wpa_supplicant via d-bus. I have not done this as masking the unit file works fine for my purposes.






share|improve this answer

































    0














    I tried following BrettB's suggestion, but it had no effect on my system. (Ubuntu 18.04.)



    However, the following did work:



    sudo systemctl disable wpa_supplicant





    share|improve this answer































      0














      You can stop it at any time after booting with
      sudo service wpa_supplicant stop






      share|improve this answer








      New contributor



      John Fro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















        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%2f306276%2fmake-systemd-stop-starting-unwanted-wpa-supplicant-service%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        4














        I ran into the same issue as yours. After some digging, I found a folder called:



        /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service


        This is file is used to allow the service to be activated by d-bus. d-bus can activate the service even if it is disabled. I confirmed that this was happening by re-naming the file, and then rebooting. I saw that at this point wpa_supplicant had not been started! To chase the issue down further would required finding out what program is activating wpa_supplicant via d-bus. I have not done this as masking the unit file works fine for my purposes.






        share|improve this answer






























          4














          I ran into the same issue as yours. After some digging, I found a folder called:



          /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service


          This is file is used to allow the service to be activated by d-bus. d-bus can activate the service even if it is disabled. I confirmed that this was happening by re-naming the file, and then rebooting. I saw that at this point wpa_supplicant had not been started! To chase the issue down further would required finding out what program is activating wpa_supplicant via d-bus. I have not done this as masking the unit file works fine for my purposes.






          share|improve this answer




























            4












            4








            4







            I ran into the same issue as yours. After some digging, I found a folder called:



            /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service


            This is file is used to allow the service to be activated by d-bus. d-bus can activate the service even if it is disabled. I confirmed that this was happening by re-naming the file, and then rebooting. I saw that at this point wpa_supplicant had not been started! To chase the issue down further would required finding out what program is activating wpa_supplicant via d-bus. I have not done this as masking the unit file works fine for my purposes.






            share|improve this answer















            I ran into the same issue as yours. After some digging, I found a folder called:



            /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service


            This is file is used to allow the service to be activated by d-bus. d-bus can activate the service even if it is disabled. I confirmed that this was happening by re-naming the file, and then rebooting. I saw that at this point wpa_supplicant had not been started! To chase the issue down further would required finding out what program is activating wpa_supplicant via d-bus. I have not done this as masking the unit file works fine for my purposes.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Apr 16 at 14:40









            Rui F Ribeiro

            42.6k1689150




            42.6k1689150










            answered Jan 20 '17 at 18:20









            BrettBBrettB

            412




            412

























                0














                I tried following BrettB's suggestion, but it had no effect on my system. (Ubuntu 18.04.)



                However, the following did work:



                sudo systemctl disable wpa_supplicant





                share|improve this answer




























                  0














                  I tried following BrettB's suggestion, but it had no effect on my system. (Ubuntu 18.04.)



                  However, the following did work:



                  sudo systemctl disable wpa_supplicant





                  share|improve this answer


























                    0












                    0








                    0







                    I tried following BrettB's suggestion, but it had no effect on my system. (Ubuntu 18.04.)



                    However, the following did work:



                    sudo systemctl disable wpa_supplicant





                    share|improve this answer













                    I tried following BrettB's suggestion, but it had no effect on my system. (Ubuntu 18.04.)



                    However, the following did work:



                    sudo systemctl disable wpa_supplicant






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Apr 10 at 22:07









                    Mike NakisMike Nakis

                    1012




                    1012























                        0














                        You can stop it at any time after booting with
                        sudo service wpa_supplicant stop






                        share|improve this answer








                        New contributor



                        John Fro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                        Check out our Code of Conduct.
























                          0














                          You can stop it at any time after booting with
                          sudo service wpa_supplicant stop






                          share|improve this answer








                          New contributor



                          John Fro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.






















                            0












                            0








                            0







                            You can stop it at any time after booting with
                            sudo service wpa_supplicant stop






                            share|improve this answer








                            New contributor



                            John Fro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            You can stop it at any time after booting with
                            sudo service wpa_supplicant stop







                            share|improve this answer








                            New contributor



                            John Fro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.








                            share|improve this answer



                            share|improve this answer






                            New contributor



                            John Fro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.








                            answered 2 hours ago









                            John FroJohn Fro

                            1




                            1




                            New contributor



                            John Fro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.




                            New contributor




                            John Fro is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.
































                                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.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f306276%2fmake-systemd-stop-starting-unwanted-wpa-supplicant-service%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







                                HolErAnrtivCnj6x6,z vwp6Qwy,9
                                tS5BsRimcLyQ,qCi4z3ubb,RR4,6M1LBE 4kbUJYaQCICmTjE13fTjbjZB6qPn

                                Popular posts from this blog

                                Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                                Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                                Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...