What is the meaning of ownership of a process on a window?












0














In manpage of xdotool




getwindowpid [window]


Output the PID owning a given window. This requires effort from the
application owning a window and may not work for all windows. This
uses _NET_WM_PID property of the window. See "EXTENDED WINDOW MANAGER
HINTS" below for more information.




When a process is said to own a window, what does that mean? I have several guesses about it:




  • Is the process the one which has created the window?


  • A window is not a process, so ownership can't imply the parent-child relation between processes.


  • what is the relation between a window of a process and the controlling terminal of the same process ('s session)? Is a window of a process related to terminal related signals (SIGINT, SIGHUP, SIGQUIT)?



Thanks.










share|improve this question


















  • 3




    It doesn't mean anything; any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows.
    – mosvy
    Dec 5 '18 at 17:38


















0














In manpage of xdotool




getwindowpid [window]


Output the PID owning a given window. This requires effort from the
application owning a window and may not work for all windows. This
uses _NET_WM_PID property of the window. See "EXTENDED WINDOW MANAGER
HINTS" below for more information.




When a process is said to own a window, what does that mean? I have several guesses about it:




  • Is the process the one which has created the window?


  • A window is not a process, so ownership can't imply the parent-child relation between processes.


  • what is the relation between a window of a process and the controlling terminal of the same process ('s session)? Is a window of a process related to terminal related signals (SIGINT, SIGHUP, SIGQUIT)?



Thanks.










share|improve this question


















  • 3




    It doesn't mean anything; any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows.
    – mosvy
    Dec 5 '18 at 17:38
















0












0








0







In manpage of xdotool




getwindowpid [window]


Output the PID owning a given window. This requires effort from the
application owning a window and may not work for all windows. This
uses _NET_WM_PID property of the window. See "EXTENDED WINDOW MANAGER
HINTS" below for more information.




When a process is said to own a window, what does that mean? I have several guesses about it:




  • Is the process the one which has created the window?


  • A window is not a process, so ownership can't imply the parent-child relation between processes.


  • what is the relation between a window of a process and the controlling terminal of the same process ('s session)? Is a window of a process related to terminal related signals (SIGINT, SIGHUP, SIGQUIT)?



Thanks.










share|improve this question













In manpage of xdotool




getwindowpid [window]


Output the PID owning a given window. This requires effort from the
application owning a window and may not work for all windows. This
uses _NET_WM_PID property of the window. See "EXTENDED WINDOW MANAGER
HINTS" below for more information.




When a process is said to own a window, what does that mean? I have several guesses about it:




  • Is the process the one which has created the window?


  • A window is not a process, so ownership can't imply the parent-child relation between processes.


  • what is the relation between a window of a process and the controlling terminal of the same process ('s session)? Is a window of a process related to terminal related signals (SIGINT, SIGHUP, SIGQUIT)?



Thanks.







x11 process






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 5 '18 at 15:53









Tim

26.3k74246455




26.3k74246455








  • 3




    It doesn't mean anything; any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows.
    – mosvy
    Dec 5 '18 at 17:38
















  • 3




    It doesn't mean anything; any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows.
    – mosvy
    Dec 5 '18 at 17:38










3




3




It doesn't mean anything; any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows.
– mosvy
Dec 5 '18 at 17:38






It doesn't mean anything; any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows.
– mosvy
Dec 5 '18 at 17:38












1 Answer
1






active

oldest

votes


















0














From mosvy's comment:




any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows







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%2f486178%2fwhat-is-the-meaning-of-ownership-of-a-process-on-a-window%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














    From mosvy's comment:




    any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows







    share|improve this answer


























      0














      From mosvy's comment:




      any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows







      share|improve this answer
























        0












        0








        0






        From mosvy's comment:




        any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows







        share|improve this answer












        From mosvy's comment:




        any X11 client can set the _NET_WM_PID property on any window to whatever it likes, eg. xprop -id $WINDOWID -f _NET_WM_PID 32c -set _NET_WM_PID 1 will not make your terminal window owned by init. Processes and/or X11 clients do not own windows








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 2 days ago









        Tim

        26.3k74246455




        26.3k74246455






























            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%2f486178%2fwhat-is-the-meaning-of-ownership-of-a-process-on-a-window%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

            How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?