sudo -u user “whoami” works but not other commands
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
When I run the following it works:
sudo -u apache 'whoami'
But when I run this, it says command not found:
sudo -u apache 'ls -al ~/.ssh'
How do I fix this?
sudo centos-7
asked Feb 4 at 13:36
AlbertAlbert
1135
add a comment |
When I run the following it works:
sudo -u apache 'whoami'
But when I run this, it says command not found:
sudo -u apache 'ls -al ~/.ssh'
How do I fix this?
sudo centos-7
asked Feb 4 at 13:36
AlbertAlbert
1135
add a comment |
When I run the following it works:
sudo -u apache 'whoami'
But when I run this, it says command not found:
sudo -u apache 'ls -al ~/.ssh'
How do I fix this?
sudo centos-7
asked Feb 4 at 13:36
AlbertAlbert
1135
When I run the following it works:
sudo -u apache 'whoami'
But when I run this, it says command not found:
sudo -u apache 'ls -al ~/.ssh'
How do I fix this?
sudo centos-7
sudo centos-7
asked Feb 4 at 13:36
AlbertAlbert
1135
asked Feb 4 at 13:36
AlbertAlbert
1135
asked Feb 4 at 13:36
AlbertAlbert
1135
asked Feb 4 at 13:36
AlbertAlbert
1135
asked Feb 4 at 13:36
AlbertAlbert
1135
1135
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
sudo sees the entire ls -al ~/.ssh string as one argument and runs it as one, as if the apache user invoked
'ls -al ~/.ssh'
And this doesn't work because there is no tool named literally ls -al ~/.ssh as a whole. Your command should be more like
sudo -u apache ls -al ~/.ssh
Note this will expand ~ before sudo even starts, in the context of your actual user. This, on the other hand:
sudo -u apache ls -al ~apache/.ssh
may be what you really want.
answered Feb 4 at 13:47
Kamil MaciorowskiKamil Maciorowski
29.2k156288
add a comment |
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',
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
});
}
});
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%2fsuperuser.com%2fquestions%2f1401860%2fsudo-u-user-whoami-works-but-not-other-commands%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
sudo sees the entire ls -al ~/.ssh string as one argument and runs it as one, as if the apache user invoked
'ls -al ~/.ssh'
And this doesn't work because there is no tool named literally ls -al ~/.ssh as a whole. Your command should be more like
sudo -u apache ls -al ~/.ssh
Note this will expand ~ before sudo even starts, in the context of your actual user. This, on the other hand:
sudo -u apache ls -al ~apache/.ssh
may be what you really want.
answered Feb 4 at 13:47
Kamil MaciorowskiKamil Maciorowski
29.2k156288
add a comment |
sudo sees the entire ls -al ~/.ssh string as one argument and runs it as one, as if the apache user invoked
'ls -al ~/.ssh'
And this doesn't work because there is no tool named literally ls -al ~/.ssh as a whole. Your command should be more like
sudo -u apache ls -al ~/.ssh
Note this will expand ~ before sudo even starts, in the context of your actual user. This, on the other hand:
sudo -u apache ls -al ~apache/.ssh
may be what you really want.
answered Feb 4 at 13:47
Kamil MaciorowskiKamil Maciorowski
29.2k156288
add a comment |
sudo sees the entire ls -al ~/.ssh string as one argument and runs it as one, as if the apache user invoked
'ls -al ~/.ssh'
And this doesn't work because there is no tool named literally ls -al ~/.ssh as a whole. Your command should be more like
sudo -u apache ls -al ~/.ssh
Note this will expand ~ before sudo even starts, in the context of your actual user. This, on the other hand:
sudo -u apache ls -al ~apache/.ssh
may be what you really want.
answered Feb 4 at 13:47
Kamil MaciorowskiKamil Maciorowski
29.2k156288
sudo sees the entire ls -al ~/.ssh string as one argument and runs it as one, as if the apache user invoked
'ls -al ~/.ssh'
And this doesn't work because there is no tool named literally ls -al ~/.ssh as a whole. Your command should be more like
sudo -u apache ls -al ~/.ssh
Note this will expand ~ before sudo even starts, in the context of your actual user. This, on the other hand:
sudo -u apache ls -al ~apache/.ssh
may be what you really want.
answered Feb 4 at 13:47
Kamil MaciorowskiKamil Maciorowski
29.2k156288
answered Feb 4 at 13:47
Kamil MaciorowskiKamil Maciorowski
29.2k156288
answered Feb 4 at 13:47
Kamil MaciorowskiKamil Maciorowski
29.2k156288
answered Feb 4 at 13:47
Kamil MaciorowskiKamil Maciorowski
29.2k156288
29.2k156288
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1401860%2fsudo-u-user-whoami-works-but-not-other-commands%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
