What does chmod -u do?2019 Community Moderator ElectionWhy does chmod +w not give write permission to other(o)Is NTFS under linux able to save a linux file, with its chown and chmod settings?chmod -R 644 ~/Documentschmod: What does the `+a` parameter mean?External drive chmod does nothingWhen does chmod fail?invalid mode chmod commandRoot can't chmod?chmod - What does this command do?In Fedora what corresponds to chmod?What is a chmod equivalent of mesg

I'm the sea and the sun

How does a computer interpret real numbers?

What if a revenant (monster) gains fire resistance?

Can disgust be a key component of horror?

What does "Scientists rise up against statistical significance" mean? (Comment in Nature)

Are Captain Marvel's powers affected by Thanos' actions in Infinity War

Does an advisor owe his/her student anything? Will an advisor keep a PhD student only out of pity?

How to hide some fields of struct in C?

What is the highest possible scrabble score for placing a single tile

Why should universal income be universal?

Can I visit Japan without a visa?

Can a College of Swords bard use a Blade Flourish option on an opportunity attack provoked by their own Dissonant Whispers spell?

Biological Blimps: Propulsion

Temporarily disable WLAN internet access for children, but allow it for adults

Why would a new[] expression ever invoke a destructor?

Creepy dinosaur pc game identification

A social experiment. What is the worst that can happen?

How could a planet have erratic days?

Do the primes contain an infinite almost arithmetic progression?

Yosemite Fire Rings - What to Expect?

How do you respond to a colleague from another team when they're wrongly expecting that you'll help them?

Does Doodling or Improvising on the Piano Have Any Benefits?

How to fade a semiplane defined by line?

Can the US President recognize Israel’s sovereignty over the Golan Heights for the USA or does that need an act of Congress?



What does chmod -u do?



2019 Community Moderator ElectionWhy does chmod +w not give write permission to other(o)Is NTFS under linux able to save a linux file, with its chown and chmod settings?chmod -R 644 ~/Documentschmod: What does the `+a` parameter mean?External drive chmod does nothingWhen does chmod fail?invalid mode chmod commandRoot can't chmod?chmod - What does this command do?In Fedora what corresponds to chmod?What is a chmod equivalent of mesg










3















By accident I ran chmod -u filename and it removed all of the permissions I had on filename.



The man page does not reference a -u option. Experimenting I was able to conclude that it removes not all permissions, but just read and execute access, leaving write access intact.



So what does this do exactly?




My conclusion above is wrong, I now think that what it does is remove the permissions that the owner has, from all categories.




I think the behavior is analogous to a=u, only it is - instead of = and a can be dropped just as it can with, for instance, a+x.










share|improve this question









New contributor




y_wc is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • +1 for asking a basic question that is not in the man page.

    – jww
    2 hours ago






  • 1





    "The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo" (GNU chmod man page); POSIX is fairly obscure, but defines a "permcopy" production for the same effect.

    – Michael Homer
    2 hours ago












  • @MichaelHomer It doesn't say what it does.

    – y_wc
    2 hours ago











  • @y_wc "Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)."

    – Michael Homer
    2 hours ago












  • Yes, I read that. I don't see that it mentions what it does. It says that I can specify one of those letters. Specifying, for instance u, I'll be specifying the permissions granted to the user who owns the file. But it doesn't say what it does. What does specify even mean?

    – y_wc
    2 hours ago















3















By accident I ran chmod -u filename and it removed all of the permissions I had on filename.



The man page does not reference a -u option. Experimenting I was able to conclude that it removes not all permissions, but just read and execute access, leaving write access intact.



So what does this do exactly?




My conclusion above is wrong, I now think that what it does is remove the permissions that the owner has, from all categories.




I think the behavior is analogous to a=u, only it is - instead of = and a can be dropped just as it can with, for instance, a+x.










share|improve this question









New contributor




y_wc is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • +1 for asking a basic question that is not in the man page.

    – jww
    2 hours ago






  • 1





    "The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo" (GNU chmod man page); POSIX is fairly obscure, but defines a "permcopy" production for the same effect.

    – Michael Homer
    2 hours ago












  • @MichaelHomer It doesn't say what it does.

    – y_wc
    2 hours ago











  • @y_wc "Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)."

    – Michael Homer
    2 hours ago












  • Yes, I read that. I don't see that it mentions what it does. It says that I can specify one of those letters. Specifying, for instance u, I'll be specifying the permissions granted to the user who owns the file. But it doesn't say what it does. What does specify even mean?

    – y_wc
    2 hours ago













3












3








3








By accident I ran chmod -u filename and it removed all of the permissions I had on filename.



The man page does not reference a -u option. Experimenting I was able to conclude that it removes not all permissions, but just read and execute access, leaving write access intact.



So what does this do exactly?




My conclusion above is wrong, I now think that what it does is remove the permissions that the owner has, from all categories.




I think the behavior is analogous to a=u, only it is - instead of = and a can be dropped just as it can with, for instance, a+x.










share|improve this question









New contributor




y_wc is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












By accident I ran chmod -u filename and it removed all of the permissions I had on filename.



The man page does not reference a -u option. Experimenting I was able to conclude that it removes not all permissions, but just read and execute access, leaving write access intact.



So what does this do exactly?




My conclusion above is wrong, I now think that what it does is remove the permissions that the owner has, from all categories.




I think the behavior is analogous to a=u, only it is - instead of = and a can be dropped just as it can with, for instance, a+x.







chmod






share|improve this question









New contributor




y_wc is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




y_wc is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 hours ago







y_wc













New contributor




y_wc is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 hours ago









y_wcy_wc

425




425




New contributor




y_wc is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





y_wc is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






y_wc is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • +1 for asking a basic question that is not in the man page.

    – jww
    2 hours ago






  • 1





    "The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo" (GNU chmod man page); POSIX is fairly obscure, but defines a "permcopy" production for the same effect.

    – Michael Homer
    2 hours ago












  • @MichaelHomer It doesn't say what it does.

    – y_wc
    2 hours ago











  • @y_wc "Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)."

    – Michael Homer
    2 hours ago












  • Yes, I read that. I don't see that it mentions what it does. It says that I can specify one of those letters. Specifying, for instance u, I'll be specifying the permissions granted to the user who owns the file. But it doesn't say what it does. What does specify even mean?

    – y_wc
    2 hours ago

















  • +1 for asking a basic question that is not in the man page.

    – jww
    2 hours ago






  • 1





    "The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo" (GNU chmod man page); POSIX is fairly obscure, but defines a "permcopy" production for the same effect.

    – Michael Homer
    2 hours ago












  • @MichaelHomer It doesn't say what it does.

    – y_wc
    2 hours ago











  • @y_wc "Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)."

    – Michael Homer
    2 hours ago












  • Yes, I read that. I don't see that it mentions what it does. It says that I can specify one of those letters. Specifying, for instance u, I'll be specifying the permissions granted to the user who owns the file. But it doesn't say what it does. What does specify even mean?

    – y_wc
    2 hours ago
















+1 for asking a basic question that is not in the man page.

– jww
2 hours ago





+1 for asking a basic question that is not in the man page.

– jww
2 hours ago




1




1





"The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo" (GNU chmod man page); POSIX is fairly obscure, but defines a "permcopy" production for the same effect.

– Michael Homer
2 hours ago






"The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo" (GNU chmod man page); POSIX is fairly obscure, but defines a "permcopy" production for the same effect.

– Michael Homer
2 hours ago














@MichaelHomer It doesn't say what it does.

– y_wc
2 hours ago





@MichaelHomer It doesn't say what it does.

– y_wc
2 hours ago













@y_wc "Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)."

– Michael Homer
2 hours ago






@y_wc "Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)."

– Michael Homer
2 hours ago














Yes, I read that. I don't see that it mentions what it does. It says that I can specify one of those letters. Specifying, for instance u, I'll be specifying the permissions granted to the user who owns the file. But it doesn't say what it does. What does specify even mean?

– y_wc
2 hours ago





Yes, I read that. I don't see that it mentions what it does. It says that I can specify one of those letters. Specifying, for instance u, I'll be specifying the permissions granted to the user who owns the file. But it doesn't say what it does. What does specify even mean?

– y_wc
2 hours ago










2 Answers
2






active

oldest

votes


















4














This is not an option, but a standard (but uncommon) way of specifying the permissions. It means to remove (-) the permissions associated with the file owner (u), for all users (no preceding u, g, or o). This is documented in the man page.



GNU chmod's man page documents this as:




The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo




and later




Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)




So -u means to remove (-) whatever permissions are currently enabled for the owner (u) for everybody (equivalently to a-u, except honouring the current umask). While that's not often going to be very useful, the analogous chmod +u will sometimes be, to copy the permissions from the owner to others when operating recursively, for example.




It's also documented in POSIX, but more obscurely defined: the permission specification is broadly who[+-=]perms (or a number), and the effect of those are further specified:




The permcopy symbols u, g, and o shall represent the current permissions associated with the user, group, and other parts of the file mode bits, respectively. For the remainder of this section, perm refers to the non-terminals perm and permcopy in the grammar.




and then




-



...
If who is not specified, the file mode bits represented by perm for the owner, group, and other permissions, except for those with corresponding bits in the file mode creation mask of the invoking process, shall be cleared.







share|improve this answer

























  • Thanks, Michael. The POSIX documentation is convincing. The GNU however... Please see this comment of mine. I don't see how what comes after "So" follows from what's before. perms can be u, that I got. Yes, u specifies the permissions or the owner. But how does it follow that -u removes the permissions of the owner (modulus umask) from all users?

    – y_wc
    2 hours ago











  • Because that's what - always does: it removes the specified permissions from the specified class of users. -u is exactly analogous to -w or (closer) to ugo-u.

    – Michael Homer
    2 hours ago











  • I was about to say I didn't come here to discuss documentation and that I was happy to just understand what's going on, but the docs just clicked. Thanks.

    – y_wc
    2 hours ago











  • Could I trouble you with another chmod documentation question? Let me know if you think this deserves a seperate question. "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. " This, to me, is saying that, given a directory whose owner has only write access, chmod u=rx directory will leave the owner's permissions as rwx. But that's not what happens, instead they become the expected r-x. Am I misinterpreting someting?

    – y_wc
    2 hours ago











  • It's saying that the setuid/setgid (s) bits are left alone if you don't mention them, and anything else you didn't specify is removed.

    – Michael Homer
    2 hours ago


















0














The answer is little bit similar to https://unix.stackexchange.com/a/429424/255251.



chmod -u file_name


doesn't removes all permission, but it consider umask value.



umask
0022
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file
chmod -u file
chmod: file: new permissions are ----w--w-, not ---------
ls -l file
-----w--w- 1 user user 4 Feb 25 15:17 file


Now change umask value



umask 777
chmod 777 file
chmod -u file
chmod: file: new permissions are rwxrwxrwx, not ---------
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file





share|improve this answer


















  • 1





    Instructive, good to know and very useful, but I think this isn't really the issue, although it is very much related. Thanks.

    – y_wc
    2 hours ago










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
);



);






y_wc is a new contributor. Be nice, and check out our Code of Conduct.









draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508104%2fwhat-does-chmod-u-do%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









4














This is not an option, but a standard (but uncommon) way of specifying the permissions. It means to remove (-) the permissions associated with the file owner (u), for all users (no preceding u, g, or o). This is documented in the man page.



GNU chmod's man page documents this as:




The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo




and later




Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)




So -u means to remove (-) whatever permissions are currently enabled for the owner (u) for everybody (equivalently to a-u, except honouring the current umask). While that's not often going to be very useful, the analogous chmod +u will sometimes be, to copy the permissions from the owner to others when operating recursively, for example.




It's also documented in POSIX, but more obscurely defined: the permission specification is broadly who[+-=]perms (or a number), and the effect of those are further specified:




The permcopy symbols u, g, and o shall represent the current permissions associated with the user, group, and other parts of the file mode bits, respectively. For the remainder of this section, perm refers to the non-terminals perm and permcopy in the grammar.




and then




-



...
If who is not specified, the file mode bits represented by perm for the owner, group, and other permissions, except for those with corresponding bits in the file mode creation mask of the invoking process, shall be cleared.







share|improve this answer

























  • Thanks, Michael. The POSIX documentation is convincing. The GNU however... Please see this comment of mine. I don't see how what comes after "So" follows from what's before. perms can be u, that I got. Yes, u specifies the permissions or the owner. But how does it follow that -u removes the permissions of the owner (modulus umask) from all users?

    – y_wc
    2 hours ago











  • Because that's what - always does: it removes the specified permissions from the specified class of users. -u is exactly analogous to -w or (closer) to ugo-u.

    – Michael Homer
    2 hours ago











  • I was about to say I didn't come here to discuss documentation and that I was happy to just understand what's going on, but the docs just clicked. Thanks.

    – y_wc
    2 hours ago











  • Could I trouble you with another chmod documentation question? Let me know if you think this deserves a seperate question. "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. " This, to me, is saying that, given a directory whose owner has only write access, chmod u=rx directory will leave the owner's permissions as rwx. But that's not what happens, instead they become the expected r-x. Am I misinterpreting someting?

    – y_wc
    2 hours ago











  • It's saying that the setuid/setgid (s) bits are left alone if you don't mention them, and anything else you didn't specify is removed.

    – Michael Homer
    2 hours ago















4














This is not an option, but a standard (but uncommon) way of specifying the permissions. It means to remove (-) the permissions associated with the file owner (u), for all users (no preceding u, g, or o). This is documented in the man page.



GNU chmod's man page documents this as:




The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo




and later




Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)




So -u means to remove (-) whatever permissions are currently enabled for the owner (u) for everybody (equivalently to a-u, except honouring the current umask). While that's not often going to be very useful, the analogous chmod +u will sometimes be, to copy the permissions from the owner to others when operating recursively, for example.




It's also documented in POSIX, but more obscurely defined: the permission specification is broadly who[+-=]perms (or a number), and the effect of those are further specified:




The permcopy symbols u, g, and o shall represent the current permissions associated with the user, group, and other parts of the file mode bits, respectively. For the remainder of this section, perm refers to the non-terminals perm and permcopy in the grammar.




and then




-



...
If who is not specified, the file mode bits represented by perm for the owner, group, and other permissions, except for those with corresponding bits in the file mode creation mask of the invoking process, shall be cleared.







share|improve this answer

























  • Thanks, Michael. The POSIX documentation is convincing. The GNU however... Please see this comment of mine. I don't see how what comes after "So" follows from what's before. perms can be u, that I got. Yes, u specifies the permissions or the owner. But how does it follow that -u removes the permissions of the owner (modulus umask) from all users?

    – y_wc
    2 hours ago











  • Because that's what - always does: it removes the specified permissions from the specified class of users. -u is exactly analogous to -w or (closer) to ugo-u.

    – Michael Homer
    2 hours ago











  • I was about to say I didn't come here to discuss documentation and that I was happy to just understand what's going on, but the docs just clicked. Thanks.

    – y_wc
    2 hours ago











  • Could I trouble you with another chmod documentation question? Let me know if you think this deserves a seperate question. "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. " This, to me, is saying that, given a directory whose owner has only write access, chmod u=rx directory will leave the owner's permissions as rwx. But that's not what happens, instead they become the expected r-x. Am I misinterpreting someting?

    – y_wc
    2 hours ago











  • It's saying that the setuid/setgid (s) bits are left alone if you don't mention them, and anything else you didn't specify is removed.

    – Michael Homer
    2 hours ago













4












4








4







This is not an option, but a standard (but uncommon) way of specifying the permissions. It means to remove (-) the permissions associated with the file owner (u), for all users (no preceding u, g, or o). This is documented in the man page.



GNU chmod's man page documents this as:




The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo




and later




Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)




So -u means to remove (-) whatever permissions are currently enabled for the owner (u) for everybody (equivalently to a-u, except honouring the current umask). While that's not often going to be very useful, the analogous chmod +u will sometimes be, to copy the permissions from the owner to others when operating recursively, for example.




It's also documented in POSIX, but more obscurely defined: the permission specification is broadly who[+-=]perms (or a number), and the effect of those are further specified:




The permcopy symbols u, g, and o shall represent the current permissions associated with the user, group, and other parts of the file mode bits, respectively. For the remainder of this section, perm refers to the non-terminals perm and permcopy in the grammar.




and then




-



...
If who is not specified, the file mode bits represented by perm for the owner, group, and other permissions, except for those with corresponding bits in the file mode creation mask of the invoking process, shall be cleared.







share|improve this answer















This is not an option, but a standard (but uncommon) way of specifying the permissions. It means to remove (-) the permissions associated with the file owner (u), for all users (no preceding u, g, or o). This is documented in the man page.



GNU chmod's man page documents this as:




The format of a symbolic mode is [ugoa...][[-+=][perms...]...], where perms is either zero or more letters from the set rwxXst, or a single letter from the set ugo




and later




Instead of one or more of these letters, you can specify exactly one of the letters ugo: the permissions granted to the user who owns the file (u), the permissions granted to other users who are members of the file's group (g), and the permissions granted to users that are in neither of the two preceding categories (o)




So -u means to remove (-) whatever permissions are currently enabled for the owner (u) for everybody (equivalently to a-u, except honouring the current umask). While that's not often going to be very useful, the analogous chmod +u will sometimes be, to copy the permissions from the owner to others when operating recursively, for example.




It's also documented in POSIX, but more obscurely defined: the permission specification is broadly who[+-=]perms (or a number), and the effect of those are further specified:




The permcopy symbols u, g, and o shall represent the current permissions associated with the user, group, and other parts of the file mode bits, respectively. For the remainder of this section, perm refers to the non-terminals perm and permcopy in the grammar.




and then




-



...
If who is not specified, the file mode bits represented by perm for the owner, group, and other permissions, except for those with corresponding bits in the file mode creation mask of the invoking process, shall be cleared.








share|improve this answer














share|improve this answer



share|improve this answer








edited 2 hours ago

























answered 2 hours ago









Michael HomerMichael Homer

50.1k8137175




50.1k8137175












  • Thanks, Michael. The POSIX documentation is convincing. The GNU however... Please see this comment of mine. I don't see how what comes after "So" follows from what's before. perms can be u, that I got. Yes, u specifies the permissions or the owner. But how does it follow that -u removes the permissions of the owner (modulus umask) from all users?

    – y_wc
    2 hours ago











  • Because that's what - always does: it removes the specified permissions from the specified class of users. -u is exactly analogous to -w or (closer) to ugo-u.

    – Michael Homer
    2 hours ago











  • I was about to say I didn't come here to discuss documentation and that I was happy to just understand what's going on, but the docs just clicked. Thanks.

    – y_wc
    2 hours ago











  • Could I trouble you with another chmod documentation question? Let me know if you think this deserves a seperate question. "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. " This, to me, is saying that, given a directory whose owner has only write access, chmod u=rx directory will leave the owner's permissions as rwx. But that's not what happens, instead they become the expected r-x. Am I misinterpreting someting?

    – y_wc
    2 hours ago











  • It's saying that the setuid/setgid (s) bits are left alone if you don't mention them, and anything else you didn't specify is removed.

    – Michael Homer
    2 hours ago

















  • Thanks, Michael. The POSIX documentation is convincing. The GNU however... Please see this comment of mine. I don't see how what comes after "So" follows from what's before. perms can be u, that I got. Yes, u specifies the permissions or the owner. But how does it follow that -u removes the permissions of the owner (modulus umask) from all users?

    – y_wc
    2 hours ago











  • Because that's what - always does: it removes the specified permissions from the specified class of users. -u is exactly analogous to -w or (closer) to ugo-u.

    – Michael Homer
    2 hours ago











  • I was about to say I didn't come here to discuss documentation and that I was happy to just understand what's going on, but the docs just clicked. Thanks.

    – y_wc
    2 hours ago











  • Could I trouble you with another chmod documentation question? Let me know if you think this deserves a seperate question. "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. " This, to me, is saying that, given a directory whose owner has only write access, chmod u=rx directory will leave the owner's permissions as rwx. But that's not what happens, instead they become the expected r-x. Am I misinterpreting someting?

    – y_wc
    2 hours ago











  • It's saying that the setuid/setgid (s) bits are left alone if you don't mention them, and anything else you didn't specify is removed.

    – Michael Homer
    2 hours ago
















Thanks, Michael. The POSIX documentation is convincing. The GNU however... Please see this comment of mine. I don't see how what comes after "So" follows from what's before. perms can be u, that I got. Yes, u specifies the permissions or the owner. But how does it follow that -u removes the permissions of the owner (modulus umask) from all users?

– y_wc
2 hours ago





Thanks, Michael. The POSIX documentation is convincing. The GNU however... Please see this comment of mine. I don't see how what comes after "So" follows from what's before. perms can be u, that I got. Yes, u specifies the permissions or the owner. But how does it follow that -u removes the permissions of the owner (modulus umask) from all users?

– y_wc
2 hours ago













Because that's what - always does: it removes the specified permissions from the specified class of users. -u is exactly analogous to -w or (closer) to ugo-u.

– Michael Homer
2 hours ago





Because that's what - always does: it removes the specified permissions from the specified class of users. -u is exactly analogous to -w or (closer) to ugo-u.

– Michael Homer
2 hours ago













I was about to say I didn't come here to discuss documentation and that I was happy to just understand what's going on, but the docs just clicked. Thanks.

– y_wc
2 hours ago





I was about to say I didn't come here to discuss documentation and that I was happy to just understand what's going on, but the docs just clicked. Thanks.

– y_wc
2 hours ago













Could I trouble you with another chmod documentation question? Let me know if you think this deserves a seperate question. "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. " This, to me, is saying that, given a directory whose owner has only write access, chmod u=rx directory will leave the owner's permissions as rwx. But that's not what happens, instead they become the expected r-x. Am I misinterpreting someting?

– y_wc
2 hours ago





Could I trouble you with another chmod documentation question? Let me know if you think this deserves a seperate question. "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. " This, to me, is saying that, given a directory whose owner has only write access, chmod u=rx directory will leave the owner's permissions as rwx. But that's not what happens, instead they become the expected r-x. Am I misinterpreting someting?

– y_wc
2 hours ago













It's saying that the setuid/setgid (s) bits are left alone if you don't mention them, and anything else you didn't specify is removed.

– Michael Homer
2 hours ago





It's saying that the setuid/setgid (s) bits are left alone if you don't mention them, and anything else you didn't specify is removed.

– Michael Homer
2 hours ago













0














The answer is little bit similar to https://unix.stackexchange.com/a/429424/255251.



chmod -u file_name


doesn't removes all permission, but it consider umask value.



umask
0022
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file
chmod -u file
chmod: file: new permissions are ----w--w-, not ---------
ls -l file
-----w--w- 1 user user 4 Feb 25 15:17 file


Now change umask value



umask 777
chmod 777 file
chmod -u file
chmod: file: new permissions are rwxrwxrwx, not ---------
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file





share|improve this answer


















  • 1





    Instructive, good to know and very useful, but I think this isn't really the issue, although it is very much related. Thanks.

    – y_wc
    2 hours ago















0














The answer is little bit similar to https://unix.stackexchange.com/a/429424/255251.



chmod -u file_name


doesn't removes all permission, but it consider umask value.



umask
0022
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file
chmod -u file
chmod: file: new permissions are ----w--w-, not ---------
ls -l file
-----w--w- 1 user user 4 Feb 25 15:17 file


Now change umask value



umask 777
chmod 777 file
chmod -u file
chmod: file: new permissions are rwxrwxrwx, not ---------
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file





share|improve this answer


















  • 1





    Instructive, good to know and very useful, but I think this isn't really the issue, although it is very much related. Thanks.

    – y_wc
    2 hours ago













0












0








0







The answer is little bit similar to https://unix.stackexchange.com/a/429424/255251.



chmod -u file_name


doesn't removes all permission, but it consider umask value.



umask
0022
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file
chmod -u file
chmod: file: new permissions are ----w--w-, not ---------
ls -l file
-----w--w- 1 user user 4 Feb 25 15:17 file


Now change umask value



umask 777
chmod 777 file
chmod -u file
chmod: file: new permissions are rwxrwxrwx, not ---------
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file





share|improve this answer













The answer is little bit similar to https://unix.stackexchange.com/a/429424/255251.



chmod -u file_name


doesn't removes all permission, but it consider umask value.



umask
0022
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file
chmod -u file
chmod: file: new permissions are ----w--w-, not ---------
ls -l file
-----w--w- 1 user user 4 Feb 25 15:17 file


Now change umask value



umask 777
chmod 777 file
chmod -u file
chmod: file: new permissions are rwxrwxrwx, not ---------
ls -l file
-rwxrwxrwx 1 user user 4 Feb 25 15:17 file






share|improve this answer












share|improve this answer



share|improve this answer










answered 2 hours ago









Prvt_YadvPrvt_Yadv

2,88031227




2,88031227







  • 1





    Instructive, good to know and very useful, but I think this isn't really the issue, although it is very much related. Thanks.

    – y_wc
    2 hours ago












  • 1





    Instructive, good to know and very useful, but I think this isn't really the issue, although it is very much related. Thanks.

    – y_wc
    2 hours ago







1




1





Instructive, good to know and very useful, but I think this isn't really the issue, although it is very much related. Thanks.

– y_wc
2 hours ago





Instructive, good to know and very useful, but I think this isn't really the issue, although it is very much related. Thanks.

– y_wc
2 hours ago










y_wc is a new contributor. Be nice, and check out our Code of Conduct.









draft saved

draft discarded


















y_wc is a new contributor. Be nice, and check out our Code of Conduct.












y_wc is a new contributor. Be nice, and check out our Code of Conduct.











y_wc is a new contributor. Be nice, and check out our Code of Conduct.














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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508104%2fwhat-does-chmod-u-do%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

Францішак Багушэвіч Змест Сям'я | Біяграфія | Творчасць | Мова Багушэвіча | Ацэнкі дзейнасці | Цікавыя факты | Спадчына | Выбраная бібліяграфія | Ушанаванне памяці | У філатэліі | Зноскі | Літаратура | Спасылкі | НавігацыяЛяхоўскі У. Рупіўся дзеля Бога і людзей: Жыццёвы шлях Лявона Вітан-Дубейкаўскага // Вольскі і Памідораў з песняй пра немца Адвакат, паэт, народны заступнік Ашмянскі веснікВ Минске появится площадь Богушевича и улица Сырокомли, Белорусская деловая газета, 19 июля 2001 г.Айцец беларускай нацыянальнай ідэі паўстаў у бронзе Сяргей Аляксандравіч Адашкевіч (1918, Мінск). 80-я гады. Бюст «Францішак Багушэвіч».Яўген Мікалаевіч Ціхановіч. «Партрэт Францішка Багушэвіча»Мікола Мікалаевіч Купава. «Партрэт зачынальніка новай беларускай літаратуры Францішка Багушэвіча»Уладзімір Іванавіч Мелехаў. На помніку «Змагарам за родную мову» Барэльеф «Францішак Багушэвіч»Памяць пра Багушэвіча на Віленшчыне Страчаная сталіца. Беларускія шыльды на вуліцах Вільні«Krynica». Ideologia i przywódcy białoruskiego katolicyzmuФранцішак БагушэвічТворы на knihi.comТворы Францішка Багушэвіча на bellib.byСодаль Уладзімір. Францішак Багушэвіч на Лідчыне;Луцкевіч Антон. Жыцьцё і творчасьць Фр. Багушэвіча ў успамінах ягоных сучасьнікаў // Запісы Беларускага Навуковага таварыства. Вільня, 1938. Сшытак 1. С. 16-34.Большая российская1188761710000 0000 5537 633Xn9209310021619551927869394п

Беларусь Змест Назва Гісторыя Геаграфія Сімволіка Дзяржаўны лад Палітычныя партыі Міжнароднае становішча і знешняя палітыка Адміністрацыйны падзел Насельніцтва Эканоміка Культура і грамадства Сацыяльная сфера Узброеныя сілы Заўвагі Літаратура Спасылкі НавігацыяHGЯOiТоп-2011 г. (па версіі ej.by)Топ-2013 г. (па версіі ej.by)Топ-2016 г. (па версіі ej.by)Топ-2017 г. (па версіі ej.by)Нацыянальны статыстычны камітэт Рэспублікі БеларусьШчыльнасць насельніцтва па краінахhttp://naviny.by/rubrics/society/2011/09/16/ic_articles_116_175144/А. Калечыц, У. Ксяндзоў. Спробы засялення краю неандэртальскім чалавекам.І ў Менску былі мамантыА. Калечыц, У. Ксяндзоў. Старажытны каменны век (палеаліт). Першапачатковае засяленне тэрыторыіГ. Штыхаў. Балты і славяне ў VI—VIII стст.М. Клімаў. Полацкае княства ў IX—XI стст.Г. Штыхаў, В. Ляўко. Палітычная гісторыя Полацкай зямліГ. Штыхаў. Дзяржаўны лад у землях-княствахГ. Штыхаў. Дзяржаўны лад у землях-княствахБеларускія землі ў складзе Вялікага Княства ЛітоўскагаЛюблінская унія 1569 г."The Early Stages of Independence"Zapomniane prawdy25 гадоў таму было аб'яўлена, што Язэп Пілсудскі — беларус (фота)Наша вадаДакументы ЧАЭС: Забруджванне тэрыторыі Беларусі « ЧАЭС Зона адчужэнняСведения о политических партиях, зарегистрированных в Республике Беларусь // Министерство юстиции Республики БеларусьСтатыстычны бюлетэнь „Полаўзроставая структура насельніцтва Рэспублікі Беларусь на 1 студзеня 2012 года і сярэднегадовая колькасць насельніцтва за 2011 год“Индекс человеческого развития Беларуси — не было бы нижеБеларусь занимает первое место в СНГ по индексу развития с учетом гендерного факцёраНацыянальны статыстычны камітэт Рэспублікі БеларусьКанстытуцыя РБ. Артыкул 17Трансфармацыйныя задачы БеларусіВыйсце з крызісу — далейшае рэфармаванне Беларускі рубель — сусветны лідар па дэвальвацыяхПра змену коштаў у кастрычніку 2011 г.Бядней за беларусаў у СНД толькі таджыкіСярэдні заробак у верасні дасягнуў 2,26 мільёна рублёўЭканомікаГаласуем за ТОП-100 беларускай прозыСучасныя беларускія мастакіАрхитектура Беларуси BELARUS.BYА. Каханоўскі. Культура Беларусі ўсярэдзіне XVII—XVIII ст.Анталогія беларускай народнай песні, гуказапісы спеваўБеларускія Музычныя IнструментыБеларускі рок, які мы страцілі. Топ-10 гуртоў«Мясцовы час» — нязгаслая легенда беларускай рок-музыкіСЯРГЕЙ БУДКІН. МЫ НЯ ЗНАЕМ СВАЁЙ МУЗЫКІМ. А. Каладзінскі. НАРОДНЫ ТЭАТРМагнацкія культурныя цэнтрыПублічная дыскусія «Беларуская новая пьеса: без беларускай мовы ці беларуская?»Беларускія драматургі па-ранейшаму лепш ставяцца за мяжой, чым на радзіме«Працэс незалежнага кіно пайшоў, і дзяржаву турбуе яго непадкантрольнасць»Беларускія філосафы ў пошуках прасторыВсе идём в библиотекуАрхіваванаАб Нацыянальнай праграме даследавання і выкарыстання касмічнай прасторы ў мірных мэтах на 2008—2012 гадыУ космас — разам.У суседнім з Барысаўскім раёне пабудуюць Камандна-вымяральны пунктСвяты і абрады беларусаў«Мірныя бульбашы з малой краіны» — 5 непраўдзівых стэрэатыпаў пра БеларусьМ. Раманюк. Беларускае народнае адзеннеУ Беларусі скарачаецца колькасць злачынстваўЛукашэнка незадаволены мінскімі ўладамі Крадзяжы складаюць у Мінску каля 70% злачынстваў Узровень злачыннасці ў Мінскай вобласці — адзін з самых высокіх у краіне Генпракуратура аналізуе стан са злачыннасцю ў Беларусі па каэфіцыенце злачыннасці У Беларусі стабілізавалася крымінагеннае становішча, лічыць генпракурорЗамежнікі сталі здзяйсняць у Беларусі больш злачынстваўМУС Беларусі турбуе рост рэцыдыўнай злачыннасціЯ з ЖЭСа. Дазволіце вас абкрасці! Рэйтынг усіх службаў і падраздзяленняў ГУУС Мінгарвыканкама вырасАб КДБ РБГісторыя Аператыўна-аналітычнага цэнтра РБГісторыя ДКФРТаможняagentura.ruБеларусьBelarus.by — Афіцыйны сайт Рэспублікі БеларусьСайт урада БеларусіRadzima.org — Збор архітэктурных помнікаў, гісторыя Беларусі«Глобус Беларуси»Гербы и флаги БеларусиАсаблівасці каменнага веку на БеларусіА. Калечыц, У. Ксяндзоў. Старажытны каменны век (палеаліт). Першапачатковае засяленне тэрыторыіУ. Ксяндзоў. Сярэдні каменны век (мезаліт). Засяленне краю плямёнамі паляўнічых, рыбакоў і збіральнікаўА. Калечыц, М. Чарняўскі. Плямёны на тэрыторыі Беларусі ў новым каменным веку (неаліце)А. Калечыц, У. Ксяндзоў, М. Чарняўскі. Гаспадарчыя заняткі ў каменным векуЭ. Зайкоўскі. Духоўная культура ў каменным векуАсаблівасці бронзавага веку на БеларусіФарміраванне супольнасцей ранняга перыяду бронзавага векуФотографии БеларусиРоля беларускіх зямель ва ўтварэнні і ўмацаванні ВКЛВ. Фадзеева. З гісторыі развіцця беларускай народнай вышыўкіDMOZGran catalanaБольшая российскаяBritannica (анлайн)Швейцарскі гістарычны15325917611952699xDA123282154079143-90000 0001 2171 2080n9112870100577502ge128882171858027501086026362074122714179пппппп

ValueError: Expected n_neighbors <= n_samples, but n_samples = 1, n_neighbors = 6 (SMOTE) The 2019 Stack Overflow Developer Survey Results Are InCan SMOTE be applied over sequence of words (sentences)?ValueError when doing validation with random forestsSMOTE and multi class oversamplingLogic behind SMOTE-NC?ValueError: Error when checking target: expected dense_1 to have shape (7,) but got array with shape (1,)SmoteBoost: Should SMOTE be ran individually for each iteration/tree in the boosting?solving multi-class imbalance classification using smote and OSSUsing SMOTE for Synthetic Data generation to improve performance on unbalanced dataproblem of entry format for a simple model in KerasSVM SMOTE fit_resample() function runs forever with no result