'chmod -644' would set file permission to 000Permisions set to unknown after chmod 777What are the standard file permissions for the /etc directory(file)Cannot use sudo command, changed permission of /usr folderFile permissions won't changeHaving trouble with chmod“No such file or directory” after chmodPermission to my .sh file?What are the consequences of running chmod 755 -R on home directory?rsync + chmod multiple fileschmod 400 will not change the permissions of a file

How can I find out about the game world without meta-influencing it?

Is it possible to have battery technology that can't be duplicated?

What is the language spoken in Babylon?

A team managed by my peer is close to melting down

Simple log rotation script

Was the Lonely Mountain, where Smaug lived, a volcano?

What's the relation between у.е. to USD?

I am caught when I was about to steal some candies

Changing the PK column of a data extension without completely recreating it

Am I allowed to determine tenets of my contract as a warlock?

Did I need a visa in 2004 and 2006?

In American Politics, why is the Justice Department under the President?

A life of PhD: is it feasible?

Do Veracrypt encrypted volumes have any kind of brute force protection?

LWC: detect last element in for:each iteration

Must a CPU have a GPU if the motherboard provides a display port (when there isn't any separate video card)?

What is Gilligan's full name?

How do I properly use a function under a class?

My mom's return ticket is 3 days after I-94 expires

Boss making me feel guilty for leaving the company at the end of my internship

David slept with Bathsheba because she was pure?? What does that mean?

Can I get a photo of an Ancient Arrow?

Part of my house is inexplicably gone

Can I use 220 V outlets on a 15 ampere breaker and wire it up as 110 V?



'chmod -644' would set file permission to 000


Permisions set to unknown after chmod 777What are the standard file permissions for the /etc directory(file)Cannot use sudo command, changed permission of /usr folderFile permissions won't changeHaving trouble with chmod“No such file or directory” after chmodPermission to my .sh file?What are the consequences of running chmod 755 -R on home directory?rsync + chmod multiple fileschmod 400 will not change the permissions of a file






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








12















I had a file with 644(-rw-r--r--) and wanted to change it to 664(-rw-rw-r--), after running:



sudo chmod -664 my_file


file permissions were set to 000(----------).



Trying to change the permissions to anything different than 000 seems to be not working. What am I missing here?










share|improve this question



















  • 11





    Why do you have a - in front of 644 ? Try sudo chmod 644 my_file. -644 will remove the rights.

    – Soren A
    May 28 at 12:46

















12















I had a file with 644(-rw-r--r--) and wanted to change it to 664(-rw-rw-r--), after running:



sudo chmod -664 my_file


file permissions were set to 000(----------).



Trying to change the permissions to anything different than 000 seems to be not working. What am I missing here?










share|improve this question



















  • 11





    Why do you have a - in front of 644 ? Try sudo chmod 644 my_file. -644 will remove the rights.

    – Soren A
    May 28 at 12:46













12












12








12


1






I had a file with 644(-rw-r--r--) and wanted to change it to 664(-rw-rw-r--), after running:



sudo chmod -664 my_file


file permissions were set to 000(----------).



Trying to change the permissions to anything different than 000 seems to be not working. What am I missing here?










share|improve this question
















I had a file with 644(-rw-r--r--) and wanted to change it to 664(-rw-rw-r--), after running:



sudo chmod -664 my_file


file permissions were set to 000(----------).



Trying to change the permissions to anything different than 000 seems to be not working. What am I missing here?







command-line permissions chmod






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 30 at 5:15









Monty Harder

29616




29616










asked May 28 at 12:44









illgoforitillgoforit

636




636







  • 11





    Why do you have a - in front of 644 ? Try sudo chmod 644 my_file. -644 will remove the rights.

    – Soren A
    May 28 at 12:46












  • 11





    Why do you have a - in front of 644 ? Try sudo chmod 644 my_file. -644 will remove the rights.

    – Soren A
    May 28 at 12:46







11




11





Why do you have a - in front of 644 ? Try sudo chmod 644 my_file. -644 will remove the rights.

– Soren A
May 28 at 12:46





Why do you have a - in front of 644 ? Try sudo chmod 644 my_file. -644 will remove the rights.

– Soren A
May 28 at 12:46










1 Answer
1






active

oldest

votes


















33














You are using -664, just use 664 instead. And never use sudo when you dont need to. If that's your file, you don't need sudo:



chmod 644 my_file


When you run chmod with a - before the mode, you will remove that mode. See man chmod (emphasis mine):




The operator + causes the selected file mode bits to be added to
the existing file mode bits of each file; - causes them to be
removed
; and = causes them to be added and causes unmentioned bits
to be removed except that a directory's unmentioned set user and
group ID bits are not affected.




The numbers are:



  • 1: execute

  • 2: write

  • 4: read

So a file with 777 permissions means everyone has the right to do all three, since 1 + 2 + 4 = 7, and therefore setting the permissions to 7 means allowing read, write and execute.



If you start with a file whose mode is 777:



$ ls -l my_file 
-rwxrwxrwx 1 terdon terdon 0 May 28 13:45 my_file


And now run chmod -644, you will remove the bits 644, and end up with a file whose mode is 133:



$ chmod -644 my_file; ls -l my_file 
---x-wx-wx 1 terdon terdon 0 May 28 13:45 my_file


That's because you removed 6 (read (4) + write (2)) from the owner's permissions, leaving only 1 (execute) set, and 4 (read) from the group and other permissions. The result is a file with only execute (1) permissions for the owner, and write and execute (you unset 4, leaving 1 and 3) permissions for the rest.



Because your file presumably had the default permissions for new files, so 644, when you ran chmod -644 my_file, you removed all of the set permission bits and got a file with no permissions for anybody.



$ ls -l my_file 
-rw-r--r-- 1 terdon terdon 0 May 28 13:45 my_file
$ chmod -644 my_file
$ ls -l my_file
---------- 1 terdon terdon 0 May 28 13:45 my_file





share|improve this answer

























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    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%2faskubuntu.com%2fquestions%2f1146834%2fchmod-644-would-set-file-permission-to-000%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









    33














    You are using -664, just use 664 instead. And never use sudo when you dont need to. If that's your file, you don't need sudo:



    chmod 644 my_file


    When you run chmod with a - before the mode, you will remove that mode. See man chmod (emphasis mine):




    The operator + causes the selected file mode bits to be added to
    the existing file mode bits of each file; - causes them to be
    removed
    ; and = causes them to be added and causes unmentioned bits
    to be removed except that a directory's unmentioned set user and
    group ID bits are not affected.




    The numbers are:



    • 1: execute

    • 2: write

    • 4: read

    So a file with 777 permissions means everyone has the right to do all three, since 1 + 2 + 4 = 7, and therefore setting the permissions to 7 means allowing read, write and execute.



    If you start with a file whose mode is 777:



    $ ls -l my_file 
    -rwxrwxrwx 1 terdon terdon 0 May 28 13:45 my_file


    And now run chmod -644, you will remove the bits 644, and end up with a file whose mode is 133:



    $ chmod -644 my_file; ls -l my_file 
    ---x-wx-wx 1 terdon terdon 0 May 28 13:45 my_file


    That's because you removed 6 (read (4) + write (2)) from the owner's permissions, leaving only 1 (execute) set, and 4 (read) from the group and other permissions. The result is a file with only execute (1) permissions for the owner, and write and execute (you unset 4, leaving 1 and 3) permissions for the rest.



    Because your file presumably had the default permissions for new files, so 644, when you ran chmod -644 my_file, you removed all of the set permission bits and got a file with no permissions for anybody.



    $ ls -l my_file 
    -rw-r--r-- 1 terdon terdon 0 May 28 13:45 my_file
    $ chmod -644 my_file
    $ ls -l my_file
    ---------- 1 terdon terdon 0 May 28 13:45 my_file





    share|improve this answer





























      33














      You are using -664, just use 664 instead. And never use sudo when you dont need to. If that's your file, you don't need sudo:



      chmod 644 my_file


      When you run chmod with a - before the mode, you will remove that mode. See man chmod (emphasis mine):




      The operator + causes the selected file mode bits to be added to
      the existing file mode bits of each file; - causes them to be
      removed
      ; and = causes them to be added and causes unmentioned bits
      to be removed except that a directory's unmentioned set user and
      group ID bits are not affected.




      The numbers are:



      • 1: execute

      • 2: write

      • 4: read

      So a file with 777 permissions means everyone has the right to do all three, since 1 + 2 + 4 = 7, and therefore setting the permissions to 7 means allowing read, write and execute.



      If you start with a file whose mode is 777:



      $ ls -l my_file 
      -rwxrwxrwx 1 terdon terdon 0 May 28 13:45 my_file


      And now run chmod -644, you will remove the bits 644, and end up with a file whose mode is 133:



      $ chmod -644 my_file; ls -l my_file 
      ---x-wx-wx 1 terdon terdon 0 May 28 13:45 my_file


      That's because you removed 6 (read (4) + write (2)) from the owner's permissions, leaving only 1 (execute) set, and 4 (read) from the group and other permissions. The result is a file with only execute (1) permissions for the owner, and write and execute (you unset 4, leaving 1 and 3) permissions for the rest.



      Because your file presumably had the default permissions for new files, so 644, when you ran chmod -644 my_file, you removed all of the set permission bits and got a file with no permissions for anybody.



      $ ls -l my_file 
      -rw-r--r-- 1 terdon terdon 0 May 28 13:45 my_file
      $ chmod -644 my_file
      $ ls -l my_file
      ---------- 1 terdon terdon 0 May 28 13:45 my_file





      share|improve this answer



























        33












        33








        33







        You are using -664, just use 664 instead. And never use sudo when you dont need to. If that's your file, you don't need sudo:



        chmod 644 my_file


        When you run chmod with a - before the mode, you will remove that mode. See man chmod (emphasis mine):




        The operator + causes the selected file mode bits to be added to
        the existing file mode bits of each file; - causes them to be
        removed
        ; and = causes them to be added and causes unmentioned bits
        to be removed except that a directory's unmentioned set user and
        group ID bits are not affected.




        The numbers are:



        • 1: execute

        • 2: write

        • 4: read

        So a file with 777 permissions means everyone has the right to do all three, since 1 + 2 + 4 = 7, and therefore setting the permissions to 7 means allowing read, write and execute.



        If you start with a file whose mode is 777:



        $ ls -l my_file 
        -rwxrwxrwx 1 terdon terdon 0 May 28 13:45 my_file


        And now run chmod -644, you will remove the bits 644, and end up with a file whose mode is 133:



        $ chmod -644 my_file; ls -l my_file 
        ---x-wx-wx 1 terdon terdon 0 May 28 13:45 my_file


        That's because you removed 6 (read (4) + write (2)) from the owner's permissions, leaving only 1 (execute) set, and 4 (read) from the group and other permissions. The result is a file with only execute (1) permissions for the owner, and write and execute (you unset 4, leaving 1 and 3) permissions for the rest.



        Because your file presumably had the default permissions for new files, so 644, when you ran chmod -644 my_file, you removed all of the set permission bits and got a file with no permissions for anybody.



        $ ls -l my_file 
        -rw-r--r-- 1 terdon terdon 0 May 28 13:45 my_file
        $ chmod -644 my_file
        $ ls -l my_file
        ---------- 1 terdon terdon 0 May 28 13:45 my_file





        share|improve this answer















        You are using -664, just use 664 instead. And never use sudo when you dont need to. If that's your file, you don't need sudo:



        chmod 644 my_file


        When you run chmod with a - before the mode, you will remove that mode. See man chmod (emphasis mine):




        The operator + causes the selected file mode bits to be added to
        the existing file mode bits of each file; - causes them to be
        removed
        ; and = causes them to be added and causes unmentioned bits
        to be removed except that a directory's unmentioned set user and
        group ID bits are not affected.




        The numbers are:



        • 1: execute

        • 2: write

        • 4: read

        So a file with 777 permissions means everyone has the right to do all three, since 1 + 2 + 4 = 7, and therefore setting the permissions to 7 means allowing read, write and execute.



        If you start with a file whose mode is 777:



        $ ls -l my_file 
        -rwxrwxrwx 1 terdon terdon 0 May 28 13:45 my_file


        And now run chmod -644, you will remove the bits 644, and end up with a file whose mode is 133:



        $ chmod -644 my_file; ls -l my_file 
        ---x-wx-wx 1 terdon terdon 0 May 28 13:45 my_file


        That's because you removed 6 (read (4) + write (2)) from the owner's permissions, leaving only 1 (execute) set, and 4 (read) from the group and other permissions. The result is a file with only execute (1) permissions for the owner, and write and execute (you unset 4, leaving 1 and 3) permissions for the rest.



        Because your file presumably had the default permissions for new files, so 644, when you ran chmod -644 my_file, you removed all of the set permission bits and got a file with no permissions for anybody.



        $ ls -l my_file 
        -rw-r--r-- 1 terdon terdon 0 May 28 13:45 my_file
        $ chmod -644 my_file
        $ ls -l my_file
        ---------- 1 terdon terdon 0 May 28 13:45 my_file






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited May 30 at 10:40

























        answered May 28 at 12:46









        terdonterdon

        70.4k13147231




        70.4k13147231



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f1146834%2fchmod-644-would-set-file-permission-to-000%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

            Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

            Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

            Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020