System group to access LED subsystem





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







2















Is there a group to which a user can be added, that gives permission to write to the LED subsystem of Linux (/sys/class/leds/)?



If not, is it possible to create such a group?



I do not want to run my application as sudo.



Edit:
I only want to change permission of a few devices for which I really needed the write permission and not for the whole leds subsystem. I have posted a solution that works for me.










share|improve this question

























  • fabiobaltieri.com/2011/09/21/linux-led-subsystem

    – fixer1234
    Jan 28 at 22:24











  • Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.

    – p0kR
    Jan 29 at 23:05











  • I have a new idea how to solve my problem and will post the answer when it works like I hope.

    – p0kR
    Jan 29 at 23:10


















2















Is there a group to which a user can be added, that gives permission to write to the LED subsystem of Linux (/sys/class/leds/)?



If not, is it possible to create such a group?



I do not want to run my application as sudo.



Edit:
I only want to change permission of a few devices for which I really needed the write permission and not for the whole leds subsystem. I have posted a solution that works for me.










share|improve this question

























  • fabiobaltieri.com/2011/09/21/linux-led-subsystem

    – fixer1234
    Jan 28 at 22:24











  • Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.

    – p0kR
    Jan 29 at 23:05











  • I have a new idea how to solve my problem and will post the answer when it works like I hope.

    – p0kR
    Jan 29 at 23:10














2












2








2








Is there a group to which a user can be added, that gives permission to write to the LED subsystem of Linux (/sys/class/leds/)?



If not, is it possible to create such a group?



I do not want to run my application as sudo.



Edit:
I only want to change permission of a few devices for which I really needed the write permission and not for the whole leds subsystem. I have posted a solution that works for me.










share|improve this question
















Is there a group to which a user can be added, that gives permission to write to the LED subsystem of Linux (/sys/class/leds/)?



If not, is it possible to create such a group?



I do not want to run my application as sudo.



Edit:
I only want to change permission of a few devices for which I really needed the write permission and not for the whole leds subsystem. I have posted a solution that works for me.







linux filesystems






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 4 at 22:05







p0kR

















asked Jan 28 at 22:05









p0kRp0kR

115




115













  • fabiobaltieri.com/2011/09/21/linux-led-subsystem

    – fixer1234
    Jan 28 at 22:24











  • Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.

    – p0kR
    Jan 29 at 23:05











  • I have a new idea how to solve my problem and will post the answer when it works like I hope.

    – p0kR
    Jan 29 at 23:10



















  • fabiobaltieri.com/2011/09/21/linux-led-subsystem

    – fixer1234
    Jan 28 at 22:24











  • Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.

    – p0kR
    Jan 29 at 23:05











  • I have a new idea how to solve my problem and will post the answer when it works like I hope.

    – p0kR
    Jan 29 at 23:10

















fabiobaltieri.com/2011/09/21/linux-led-subsystem

– fixer1234
Jan 28 at 22:24





fabiobaltieri.com/2011/09/21/linux-led-subsystem

– fixer1234
Jan 28 at 22:24













Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.

– p0kR
Jan 29 at 23:05





Thank you, but that is what I am doing. But on my distribution, access to these files is limited to root.

– p0kR
Jan 29 at 23:05













I have a new idea how to solve my problem and will post the answer when it works like I hope.

– p0kR
Jan 29 at 23:10





I have a new idea how to solve my problem and will post the answer when it works like I hope.

– p0kR
Jan 29 at 23:10










1 Answer
1






active

oldest

votes


















0














I found a solution fitting my problem.
I added a udev rule like it is described in this answer to a similar question.



First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).



Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
The rule only applies to devices that match the kernel information in the field KERNEL.



The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.



My final rule:



SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"





share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399431%2fsystem-group-to-access-led-subsystem%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









    0














    I found a solution fitting my problem.
    I added a udev rule like it is described in this answer to a similar question.



    First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).



    Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
    The rule only applies to devices that match the kernel information in the field KERNEL.



    The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.



    My final rule:



    SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"





    share|improve this answer




























      0














      I found a solution fitting my problem.
      I added a udev rule like it is described in this answer to a similar question.



      First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).



      Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
      The rule only applies to devices that match the kernel information in the field KERNEL.



      The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.



      My final rule:



      SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"





      share|improve this answer


























        0












        0








        0







        I found a solution fitting my problem.
        I added a udev rule like it is described in this answer to a similar question.



        First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).



        Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
        The rule only applies to devices that match the kernel information in the field KERNEL.



        The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.



        My final rule:



        SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"





        share|improve this answer













        I found a solution fitting my problem.
        I added a udev rule like it is described in this answer to a similar question.



        First I had to create a new group called leds. Then I created the udev rule in /etc/udev/rules.d/10-buzzers.rules (I created the file by myself, it did not exist before).



        Since I wanted to only use the Buzzer LEDs of the Buzzer controllers for the Playstation 2, I optimized the rule to only affect the files for the controllers.
        The rule only applies to devices that match the kernel information in the field KERNEL.



        The rule executes chgrp and chmod that the matching device files are owned by the leds group and that the owning group has write permission.



        My final rule:



        SUBSYSTEM=="leds", KERNEL=="0003:054C:1000.[0-9]*::buzz[1-4]", ACTION=="add", RUN+="/bin/chgrp -R leds /sys%p", RUN+="/bin/chmod -R g=u /sys%p"






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 4 at 22:03









        p0kRp0kR

        115




        115






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • 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%2fsuperuser.com%2fquestions%2f1399431%2fsystem-group-to-access-led-subsystem%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

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            Origin of the phrase “under your belt”?