How to disable Xorg Logging

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











up vote
2
down vote

favorite












I'm running CentOS 6.X and 7.X machines and use GNOME Desktop extensively, the problem is that Xorg.log.* files are getting big.



I have no need in those logs, I'd like to know how I can disable them or pass -logfile /dev/null -logverbose 0 -verbose 0 to /usr/bin/X



Who and what starts X ? If I can find it I can add the flags I assume



Thank you,
Dennis.







share|improve this question















  • 1




    this doesn`t seem normal, why are the logs so big? Do they present errors?
    – vfbsilva
    May 19 at 5:56










  • No errors, use messages such as these: [ 15.955] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 connected from local host ( uid=42 gid=42 pid=2835 ) Auth name: MIT-MAGIC-COOKIE-1 ID: 682 [ 15.956] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 disconnected
    – System Group
    May 19 at 5:58















up vote
2
down vote

favorite












I'm running CentOS 6.X and 7.X machines and use GNOME Desktop extensively, the problem is that Xorg.log.* files are getting big.



I have no need in those logs, I'd like to know how I can disable them or pass -logfile /dev/null -logverbose 0 -verbose 0 to /usr/bin/X



Who and what starts X ? If I can find it I can add the flags I assume



Thank you,
Dennis.







share|improve this question















  • 1




    this doesn`t seem normal, why are the logs so big? Do they present errors?
    – vfbsilva
    May 19 at 5:56










  • No errors, use messages such as these: [ 15.955] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 connected from local host ( uid=42 gid=42 pid=2835 ) Auth name: MIT-MAGIC-COOKIE-1 ID: 682 [ 15.956] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 disconnected
    – System Group
    May 19 at 5:58













up vote
2
down vote

favorite









up vote
2
down vote

favorite











I'm running CentOS 6.X and 7.X machines and use GNOME Desktop extensively, the problem is that Xorg.log.* files are getting big.



I have no need in those logs, I'd like to know how I can disable them or pass -logfile /dev/null -logverbose 0 -verbose 0 to /usr/bin/X



Who and what starts X ? If I can find it I can add the flags I assume



Thank you,
Dennis.







share|improve this question











I'm running CentOS 6.X and 7.X machines and use GNOME Desktop extensively, the problem is that Xorg.log.* files are getting big.



I have no need in those logs, I'd like to know how I can disable them or pass -logfile /dev/null -logverbose 0 -verbose 0 to /usr/bin/X



Who and what starts X ? If I can find it I can add the flags I assume



Thank you,
Dennis.









share|improve this question










share|improve this question




share|improve this question









asked May 19 at 5:45









System Group

111




111







  • 1




    this doesn`t seem normal, why are the logs so big? Do they present errors?
    – vfbsilva
    May 19 at 5:56










  • No errors, use messages such as these: [ 15.955] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 connected from local host ( uid=42 gid=42 pid=2835 ) Auth name: MIT-MAGIC-COOKIE-1 ID: 682 [ 15.956] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 disconnected
    – System Group
    May 19 at 5:58













  • 1




    this doesn`t seem normal, why are the logs so big? Do they present errors?
    – vfbsilva
    May 19 at 5:56










  • No errors, use messages such as these: [ 15.955] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 connected from local host ( uid=42 gid=42 pid=2835 ) Auth name: MIT-MAGIC-COOKIE-1 ID: 682 [ 15.956] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 disconnected
    – System Group
    May 19 at 5:58








1




1




this doesn`t seem normal, why are the logs so big? Do they present errors?
– vfbsilva
May 19 at 5:56




this doesn`t seem normal, why are the logs so big? Do they present errors?
– vfbsilva
May 19 at 5:56












No errors, use messages such as these: [ 15.955] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 connected from local host ( uid=42 gid=42 pid=2835 ) Auth name: MIT-MAGIC-COOKIE-1 ID: 682 [ 15.956] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 disconnected
– System Group
May 19 at 5:58





No errors, use messages such as these: [ 15.955] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 connected from local host ( uid=42 gid=42 pid=2835 ) Auth name: MIT-MAGIC-COOKIE-1 ID: 682 [ 15.956] AUDIT: Thu Apr 20 16:22:35 2017: 1384: client 3 disconnected
– System Group
May 19 at 5:58











1 Answer
1






active

oldest

votes

















up vote
1
down vote













The problem seems to have been debugged here here:




Root Cause:
The messages are logged due to -audit 4 argument passed to Xorg process while gdm launches it.The options is hard-coded in new update of gdm package."




(I've seen Gnome doing really stupid things with respect to X, like hardlinked MIT cookies, but this probably tops it).



In the blog post, the solution was to replaced gdm with sddm. Any other display manager will probably also do, as will either recompiling gdm with the -audit 4 argument patched out, or patching the gdm binary with dd to overwrite the -audit 4 argument with spaces or similar.






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',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f444750%2fhow-to-disable-xorg-logging%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
    1
    down vote













    The problem seems to have been debugged here here:




    Root Cause:
    The messages are logged due to -audit 4 argument passed to Xorg process while gdm launches it.The options is hard-coded in new update of gdm package."




    (I've seen Gnome doing really stupid things with respect to X, like hardlinked MIT cookies, but this probably tops it).



    In the blog post, the solution was to replaced gdm with sddm. Any other display manager will probably also do, as will either recompiling gdm with the -audit 4 argument patched out, or patching the gdm binary with dd to overwrite the -audit 4 argument with spaces or similar.






    share|improve this answer

























      up vote
      1
      down vote













      The problem seems to have been debugged here here:




      Root Cause:
      The messages are logged due to -audit 4 argument passed to Xorg process while gdm launches it.The options is hard-coded in new update of gdm package."




      (I've seen Gnome doing really stupid things with respect to X, like hardlinked MIT cookies, but this probably tops it).



      In the blog post, the solution was to replaced gdm with sddm. Any other display manager will probably also do, as will either recompiling gdm with the -audit 4 argument patched out, or patching the gdm binary with dd to overwrite the -audit 4 argument with spaces or similar.






      share|improve this answer























        up vote
        1
        down vote










        up vote
        1
        down vote









        The problem seems to have been debugged here here:




        Root Cause:
        The messages are logged due to -audit 4 argument passed to Xorg process while gdm launches it.The options is hard-coded in new update of gdm package."




        (I've seen Gnome doing really stupid things with respect to X, like hardlinked MIT cookies, but this probably tops it).



        In the blog post, the solution was to replaced gdm with sddm. Any other display manager will probably also do, as will either recompiling gdm with the -audit 4 argument patched out, or patching the gdm binary with dd to overwrite the -audit 4 argument with spaces or similar.






        share|improve this answer













        The problem seems to have been debugged here here:




        Root Cause:
        The messages are logged due to -audit 4 argument passed to Xorg process while gdm launches it.The options is hard-coded in new update of gdm package."




        (I've seen Gnome doing really stupid things with respect to X, like hardlinked MIT cookies, but this probably tops it).



        In the blog post, the solution was to replaced gdm with sddm. Any other display manager will probably also do, as will either recompiling gdm with the -audit 4 argument patched out, or patching the gdm binary with dd to overwrite the -audit 4 argument with spaces or similar.







        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered May 20 at 5:04









        dirkt

        13.9k2930




        13.9k2930






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444750%2fhow-to-disable-xorg-logging%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            Peggy Mitchell

            Palaiologos

            The Forum (Inglewood, California)