rsync --perms - what difference does it makersync archive modeUsing rsync, how can I know what attribute of...
How do people drown while wearing a life jacket?
Plotting Autoregressive Functions / Linear Difference Equations
In MTG, was there ever a five-color deck that worked well?
Why is it to say 'paucis post diebus'?
How to win against ants
“The Fourier transform cannot measure two phases at the same frequency.” Why not?
The Game of the Century - why didn't Byrne take the rook after he forked Fischer?
Is an "are" omitted in this sentence
Why do my fried eggs start browning very fast?
How can I perform a deterministic physics simulation?
Is there a booking app or site that lets you specify your gender for shared dormitories?
Repeated! Factorials!
Is it uncompelling to continue the story with lower stakes?
How to call made-up data?
Can the Cauchy product of divergent series with itself be convergent?
Does a humanoid possessed by a ghost register as undead to a paladin's Divine Sense?
Drawing arrowtips at the end of each segment in a polygonal path
Why did the US Airways Flight 1549 passengers stay on the wings?
Is it okay to use different fingers every time while playing a song on keyboard? Is it considered a bad practice?
Can attackers change the public key of certificate during the SSL handshake
Are the related objects in an SOQL query shared?
How do I know when and if a character requires a backstory?
How do I handle a DM that plays favorites with certain players?
What does "autolyco-sentimental" mean?
rsync --perms - what difference does it make
rsync archive modeUsing rsync, how can I know what attribute of source file differed from the dest which caused the trasferrsync and xfr#1, to-chk=0/1, what do they mean?Preserve date modified on directories / folders with rsyncrsync option to disable verification?What are “matches”, “hash_hits”, and “false_alarms” in rsync output, and does “data=0” mean success?Does rsync require both source host and destination host to run rsync as client, server, or daemon?rsync --no-perms still preserves permissions and ignores umaskWhat differences are between using `-u` and not with rsync?Set permissions and owner's group for destination folder with rsync
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am on MacOS and the --perms flag doesn't appear documented when I use rsync -h..what difference does the rsync --perms flag make? Supposedly it preserves file permissions but why wouldn't rsync do that by default?
linux osx rsync
asked 3 hours ago
Alexander MillsAlexander Mills
2,4702 gold badges21 silver badges67 bronze badges
add a comment |
I am on MacOS and the --perms flag doesn't appear documented when I use rsync -h..what difference does the rsync --perms flag make? Supposedly it preserves file permissions but why wouldn't rsync do that by default?
linux osx rsync
asked 3 hours ago
Alexander MillsAlexander Mills
2,4702 gold badges21 silver badges67 bronze badges
add a comment |
I am on MacOS and the --perms flag doesn't appear documented when I use rsync -h..what difference does the rsync --perms flag make? Supposedly it preserves file permissions but why wouldn't rsync do that by default?
linux osx rsync
asked 3 hours ago
Alexander MillsAlexander Mills
2,4702 gold badges21 silver badges67 bronze badges
I am on MacOS and the --perms flag doesn't appear documented when I use rsync -h..what difference does the rsync --perms flag make? Supposedly it preserves file permissions but why wouldn't rsync do that by default?
linux osx rsync
linux osx rsync
asked 3 hours ago
Alexander MillsAlexander Mills
2,4702 gold badges21 silver badges67 bronze badges
asked 3 hours ago
Alexander MillsAlexander Mills
2,4702 gold badges21 silver badges67 bronze badges
asked 3 hours ago
Alexander MillsAlexander Mills
2,4702 gold badges21 silver badges67 bronze badges
asked 3 hours ago
Alexander MillsAlexander Mills
2,4702 gold badges21 silver badges67 bronze badges
asked 3 hours ago
Alexander MillsAlexander Mills
2,4702 gold badges21 silver badges67 bronze badges
2,4702 gold badges21 silver badges67 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The rsync -h option is a summary, not the full authoritative documentation.
I was able to find more detail by running man -P 'less -p --perms$' rsync on my MacOS's default rsync. rsync --perms copies the source permissions to the destination permissions as you posited. From the manual:
In summary: to give destination files (both old and new) the source permissions, use --perms. To give new files the destination-default permissions (while leaving existing files unchanged), make sure that the --perms option is off and use --chmod=ugo=rwX (which ensures that all non-masked bits get enabled).
A user might simply not want to copy the source file's permissions to the destination file. For example, if copying a local configuration file to a remote server, the remote might have a different set of permissions.
The above use case is supported by rsync's --chmod. Other rsync options like --executability and --no-perms suggest yet more use cases in which we can't assume every user/use case expects destination files to match the source.
answered 1 hour ago
SarandiSarandi
113 bronze badges
New contributor
Sarandi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f534057%2frsync-perms-what-difference-does-it-make%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
The rsync -h option is a summary, not the full authoritative documentation.
I was able to find more detail by running man -P 'less -p --perms$' rsync on my MacOS's default rsync. rsync --perms copies the source permissions to the destination permissions as you posited. From the manual:
In summary: to give destination files (both old and new) the source permissions, use --perms. To give new files the destination-default permissions (while leaving existing files unchanged), make sure that the --perms option is off and use --chmod=ugo=rwX (which ensures that all non-masked bits get enabled).
A user might simply not want to copy the source file's permissions to the destination file. For example, if copying a local configuration file to a remote server, the remote might have a different set of permissions.
The above use case is supported by rsync's --chmod. Other rsync options like --executability and --no-perms suggest yet more use cases in which we can't assume every user/use case expects destination files to match the source.
answered 1 hour ago
SarandiSarandi
113 bronze badges
New contributor
Sarandi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
The rsync -h option is a summary, not the full authoritative documentation.
I was able to find more detail by running man -P 'less -p --perms$' rsync on my MacOS's default rsync. rsync --perms copies the source permissions to the destination permissions as you posited. From the manual:
In summary: to give destination files (both old and new) the source permissions, use --perms. To give new files the destination-default permissions (while leaving existing files unchanged), make sure that the --perms option is off and use --chmod=ugo=rwX (which ensures that all non-masked bits get enabled).
A user might simply not want to copy the source file's permissions to the destination file. For example, if copying a local configuration file to a remote server, the remote might have a different set of permissions.
The above use case is supported by rsync's --chmod. Other rsync options like --executability and --no-perms suggest yet more use cases in which we can't assume every user/use case expects destination files to match the source.
answered 1 hour ago
SarandiSarandi
113 bronze badges
New contributor
Sarandi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
The rsync -h option is a summary, not the full authoritative documentation.
I was able to find more detail by running man -P 'less -p --perms$' rsync on my MacOS's default rsync. rsync --perms copies the source permissions to the destination permissions as you posited. From the manual:
In summary: to give destination files (both old and new) the source permissions, use --perms. To give new files the destination-default permissions (while leaving existing files unchanged), make sure that the --perms option is off and use --chmod=ugo=rwX (which ensures that all non-masked bits get enabled).
A user might simply not want to copy the source file's permissions to the destination file. For example, if copying a local configuration file to a remote server, the remote might have a different set of permissions.
The above use case is supported by rsync's --chmod. Other rsync options like --executability and --no-perms suggest yet more use cases in which we can't assume every user/use case expects destination files to match the source.
answered 1 hour ago
SarandiSarandi
113 bronze badges
New contributor
Sarandi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
The rsync -h option is a summary, not the full authoritative documentation.
I was able to find more detail by running man -P 'less -p --perms$' rsync on my MacOS's default rsync. rsync --perms copies the source permissions to the destination permissions as you posited. From the manual:
In summary: to give destination files (both old and new) the source permissions, use --perms. To give new files the destination-default permissions (while leaving existing files unchanged), make sure that the --perms option is off and use --chmod=ugo=rwX (which ensures that all non-masked bits get enabled).
A user might simply not want to copy the source file's permissions to the destination file. For example, if copying a local configuration file to a remote server, the remote might have a different set of permissions.
The above use case is supported by rsync's --chmod. Other rsync options like --executability and --no-perms suggest yet more use cases in which we can't assume every user/use case expects destination files to match the source.
answered 1 hour ago
SarandiSarandi
113 bronze badges
New contributor
Sarandi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 1 hour ago
SarandiSarandi
113 bronze badges
New contributor
Sarandi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 1 hour ago
SarandiSarandi
113 bronze badges
answered 1 hour ago
SarandiSarandi
113 bronze badges
113 bronze badges
New contributor
Sarandi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Sarandi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f534057%2frsync-perms-what-difference-does-it-make%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
