What does “t” in the permissions of the file on Linux indicate?

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











up vote
1
down vote

favorite












When I run the ls -l command on a directory, I see the following permissions for a file and I don't know what does "t" indicate in the permissions?



-r-----rwt 1 bruce bruce 28146 Oct 27 09:48 sample


sample is an ELF binary and I want to know if I have execute permissions for it.










share|improve this question

























    up vote
    1
    down vote

    favorite












    When I run the ls -l command on a directory, I see the following permissions for a file and I don't know what does "t" indicate in the permissions?



    -r-----rwt 1 bruce bruce 28146 Oct 27 09:48 sample


    sample is an ELF binary and I want to know if I have execute permissions for it.










    share|improve this question























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      When I run the ls -l command on a directory, I see the following permissions for a file and I don't know what does "t" indicate in the permissions?



      -r-----rwt 1 bruce bruce 28146 Oct 27 09:48 sample


      sample is an ELF binary and I want to know if I have execute permissions for it.










      share|improve this question













      When I run the ls -l command on a directory, I see the following permissions for a file and I don't know what does "t" indicate in the permissions?



      -r-----rwt 1 bruce bruce 28146 Oct 27 09:48 sample


      sample is an ELF binary and I want to know if I have execute permissions for it.







      linux






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 4 hours ago









      Neon Flash

      1086




      1086




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          3
          down vote



          accepted










          In short: it indicates a sticky bit. On files, it is basically useless these days - it was an optimisation hint for older OSes. It has a rather different meaning for directories.



          Lowercase t implies x while uppercase T does not.




          GNU ls is documented in its info pages (info ls), also available on the web.




          The file mode bits listed are similar to symbolic mode specifications (see Symbolic Modes). But ls combines multiple bits into the third character of each set of permissions as follows:



          ...



          t



          If the restricted deletion flag or sticky bit, and the other-executable bit, are both set. The restricted deletion flag is another name for the sticky bit. See Mode Structure.



          T



          If the restricted deletion flag or sticky bit is set but the other-executable bit is not set.



          x



          If the executable bit is set and none of the above apply.




          Lowercase t implies x (for other; user and group are shown separately) while uppercase T does not.



          Which leads us to [the mode structure](https://www.gnu.org/software/coreutils/manual/html_node/Mode-Structure.html#Mode-Structure:




          In addition to the three sets of three permissions listed above, the file mode bits have three special components, which affect only executable files (programs) and, on most systems, directories:



          ...




          1. Prevent unprivileged users from removing or renaming a file in a directory unless they own the file or the directory; this is called the restricted deletion flag for the directory, and is commonly found on world-writable directories like /tmp.



            For regular files on some older systems, save the program’s text image on the swap device so it will load more quickly when run; this is called the sticky bit.





          When used on a file, it was an old optimisation that instructs the OS to cache them after they are run. It is no longer relevant in modern OSes.






          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',
            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%2fsuperuser.com%2fquestions%2f1370474%2fwhat-does-t-in-the-permissions-of-the-file-on-linux-indicate%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
            3
            down vote



            accepted










            In short: it indicates a sticky bit. On files, it is basically useless these days - it was an optimisation hint for older OSes. It has a rather different meaning for directories.



            Lowercase t implies x while uppercase T does not.




            GNU ls is documented in its info pages (info ls), also available on the web.




            The file mode bits listed are similar to symbolic mode specifications (see Symbolic Modes). But ls combines multiple bits into the third character of each set of permissions as follows:



            ...



            t



            If the restricted deletion flag or sticky bit, and the other-executable bit, are both set. The restricted deletion flag is another name for the sticky bit. See Mode Structure.



            T



            If the restricted deletion flag or sticky bit is set but the other-executable bit is not set.



            x



            If the executable bit is set and none of the above apply.




            Lowercase t implies x (for other; user and group are shown separately) while uppercase T does not.



            Which leads us to [the mode structure](https://www.gnu.org/software/coreutils/manual/html_node/Mode-Structure.html#Mode-Structure:




            In addition to the three sets of three permissions listed above, the file mode bits have three special components, which affect only executable files (programs) and, on most systems, directories:



            ...




            1. Prevent unprivileged users from removing or renaming a file in a directory unless they own the file or the directory; this is called the restricted deletion flag for the directory, and is commonly found on world-writable directories like /tmp.



              For regular files on some older systems, save the program’s text image on the swap device so it will load more quickly when run; this is called the sticky bit.





            When used on a file, it was an old optimisation that instructs the OS to cache them after they are run. It is no longer relevant in modern OSes.






            share|improve this answer


























              up vote
              3
              down vote



              accepted










              In short: it indicates a sticky bit. On files, it is basically useless these days - it was an optimisation hint for older OSes. It has a rather different meaning for directories.



              Lowercase t implies x while uppercase T does not.




              GNU ls is documented in its info pages (info ls), also available on the web.




              The file mode bits listed are similar to symbolic mode specifications (see Symbolic Modes). But ls combines multiple bits into the third character of each set of permissions as follows:



              ...



              t



              If the restricted deletion flag or sticky bit, and the other-executable bit, are both set. The restricted deletion flag is another name for the sticky bit. See Mode Structure.



              T



              If the restricted deletion flag or sticky bit is set but the other-executable bit is not set.



              x



              If the executable bit is set and none of the above apply.




              Lowercase t implies x (for other; user and group are shown separately) while uppercase T does not.



              Which leads us to [the mode structure](https://www.gnu.org/software/coreutils/manual/html_node/Mode-Structure.html#Mode-Structure:




              In addition to the three sets of three permissions listed above, the file mode bits have three special components, which affect only executable files (programs) and, on most systems, directories:



              ...




              1. Prevent unprivileged users from removing or renaming a file in a directory unless they own the file or the directory; this is called the restricted deletion flag for the directory, and is commonly found on world-writable directories like /tmp.



                For regular files on some older systems, save the program’s text image on the swap device so it will load more quickly when run; this is called the sticky bit.





              When used on a file, it was an old optimisation that instructs the OS to cache them after they are run. It is no longer relevant in modern OSes.






              share|improve this answer
























                up vote
                3
                down vote



                accepted







                up vote
                3
                down vote



                accepted






                In short: it indicates a sticky bit. On files, it is basically useless these days - it was an optimisation hint for older OSes. It has a rather different meaning for directories.



                Lowercase t implies x while uppercase T does not.




                GNU ls is documented in its info pages (info ls), also available on the web.




                The file mode bits listed are similar to symbolic mode specifications (see Symbolic Modes). But ls combines multiple bits into the third character of each set of permissions as follows:



                ...



                t



                If the restricted deletion flag or sticky bit, and the other-executable bit, are both set. The restricted deletion flag is another name for the sticky bit. See Mode Structure.



                T



                If the restricted deletion flag or sticky bit is set but the other-executable bit is not set.



                x



                If the executable bit is set and none of the above apply.




                Lowercase t implies x (for other; user and group are shown separately) while uppercase T does not.



                Which leads us to [the mode structure](https://www.gnu.org/software/coreutils/manual/html_node/Mode-Structure.html#Mode-Structure:




                In addition to the three sets of three permissions listed above, the file mode bits have three special components, which affect only executable files (programs) and, on most systems, directories:



                ...




                1. Prevent unprivileged users from removing or renaming a file in a directory unless they own the file or the directory; this is called the restricted deletion flag for the directory, and is commonly found on world-writable directories like /tmp.



                  For regular files on some older systems, save the program’s text image on the swap device so it will load more quickly when run; this is called the sticky bit.





                When used on a file, it was an old optimisation that instructs the OS to cache them after they are run. It is no longer relevant in modern OSes.






                share|improve this answer














                In short: it indicates a sticky bit. On files, it is basically useless these days - it was an optimisation hint for older OSes. It has a rather different meaning for directories.



                Lowercase t implies x while uppercase T does not.




                GNU ls is documented in its info pages (info ls), also available on the web.




                The file mode bits listed are similar to symbolic mode specifications (see Symbolic Modes). But ls combines multiple bits into the third character of each set of permissions as follows:



                ...



                t



                If the restricted deletion flag or sticky bit, and the other-executable bit, are both set. The restricted deletion flag is another name for the sticky bit. See Mode Structure.



                T



                If the restricted deletion flag or sticky bit is set but the other-executable bit is not set.



                x



                If the executable bit is set and none of the above apply.




                Lowercase t implies x (for other; user and group are shown separately) while uppercase T does not.



                Which leads us to [the mode structure](https://www.gnu.org/software/coreutils/manual/html_node/Mode-Structure.html#Mode-Structure:




                In addition to the three sets of three permissions listed above, the file mode bits have three special components, which affect only executable files (programs) and, on most systems, directories:



                ...




                1. Prevent unprivileged users from removing or renaming a file in a directory unless they own the file or the directory; this is called the restricted deletion flag for the directory, and is commonly found on world-writable directories like /tmp.



                  For regular files on some older systems, save the program’s text image on the swap device so it will load more quickly when run; this is called the sticky bit.





                When used on a file, it was an old optimisation that instructs the OS to cache them after they are run. It is no longer relevant in modern OSes.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 4 hours ago

























                answered 4 hours ago









                Bob

                44.4k20133168




                44.4k20133168



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1370474%2fwhat-does-t-in-the-permissions-of-the-file-on-linux-indicate%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?