How to find files or folders that are inaccessible to a certain user?
I am trying to install some package in my Joomla but got an error saying "error trying to delete inaccessible file". I checked with the package developer, they said I need to make sure all files and folders under my Joomla installation is accessible to the web server.
I was reading some tutorial about find
command and its -perm
parameter, but the articles I read didn't mention how do I check permission against a particular user; Also they are all about checking files with permission but not without.
So how do I find out which file/folder is causing the CMS to throw out this "inaccessible" error?
permissions find
add a comment |
I am trying to install some package in my Joomla but got an error saying "error trying to delete inaccessible file". I checked with the package developer, they said I need to make sure all files and folders under my Joomla installation is accessible to the web server.
I was reading some tutorial about find
command and its -perm
parameter, but the articles I read didn't mention how do I check permission against a particular user; Also they are all about checking files with permission but not without.
So how do I find out which file/folder is causing the CMS to throw out this "inaccessible" error?
permissions find
add a comment |
I am trying to install some package in my Joomla but got an error saying "error trying to delete inaccessible file". I checked with the package developer, they said I need to make sure all files and folders under my Joomla installation is accessible to the web server.
I was reading some tutorial about find
command and its -perm
parameter, but the articles I read didn't mention how do I check permission against a particular user; Also they are all about checking files with permission but not without.
So how do I find out which file/folder is causing the CMS to throw out this "inaccessible" error?
permissions find
I am trying to install some package in my Joomla but got an error saying "error trying to delete inaccessible file". I checked with the package developer, they said I need to make sure all files and folders under my Joomla installation is accessible to the web server.
I was reading some tutorial about find
command and its -perm
parameter, but the articles I read didn't mention how do I check permission against a particular user; Also they are all about checking files with permission but not without.
So how do I find out which file/folder is causing the CMS to throw out this "inaccessible" error?
permissions find
permissions find
asked 9 hours ago
shenkwenshenkwen
1791212
1791212
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Access to directory is controlled by x
- execute - bit in the permissions. The issue could be due to the user having no executable permissions as owner or a group to which user belongs has no executable permissions set on the directory.
In order to use find
for that task, it's sufficient to specify -user
as the owner of the directory and -not -executable
flags.:
~$ find -type d -user $USER -not -executable
./foo/bar
./test_access
~$ ls -ld ./foo/bar ./test_access
drw-r-xr-- 2 admin admin 4096 Jan 15 03:36 ./foo/bar
drw-r--r-- 2 admin admin 4096 Jan 4 15:38 ./test_access
For cases where group part off the permissions is of interest, you could find groups the user belongs to and iterate over them:
for i in $(groups $USER | cut -d':' -f2) ; do find -type d -group "$i" -not -executable ; done
If neither case turns any potential results, the issue could be due to user not belonging to a group which has access to the directory that gives the issue.
Note also that web servers typically use www-data
user/group. You probably want to be checking permissions using that username or group name.
add a comment |
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
});
}
});
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%2faskubuntu.com%2fquestions%2f1109711%2fhow-to-find-files-or-folders-that-are-inaccessible-to-a-certain-user%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
Access to directory is controlled by x
- execute - bit in the permissions. The issue could be due to the user having no executable permissions as owner or a group to which user belongs has no executable permissions set on the directory.
In order to use find
for that task, it's sufficient to specify -user
as the owner of the directory and -not -executable
flags.:
~$ find -type d -user $USER -not -executable
./foo/bar
./test_access
~$ ls -ld ./foo/bar ./test_access
drw-r-xr-- 2 admin admin 4096 Jan 15 03:36 ./foo/bar
drw-r--r-- 2 admin admin 4096 Jan 4 15:38 ./test_access
For cases where group part off the permissions is of interest, you could find groups the user belongs to and iterate over them:
for i in $(groups $USER | cut -d':' -f2) ; do find -type d -group "$i" -not -executable ; done
If neither case turns any potential results, the issue could be due to user not belonging to a group which has access to the directory that gives the issue.
Note also that web servers typically use www-data
user/group. You probably want to be checking permissions using that username or group name.
add a comment |
Access to directory is controlled by x
- execute - bit in the permissions. The issue could be due to the user having no executable permissions as owner or a group to which user belongs has no executable permissions set on the directory.
In order to use find
for that task, it's sufficient to specify -user
as the owner of the directory and -not -executable
flags.:
~$ find -type d -user $USER -not -executable
./foo/bar
./test_access
~$ ls -ld ./foo/bar ./test_access
drw-r-xr-- 2 admin admin 4096 Jan 15 03:36 ./foo/bar
drw-r--r-- 2 admin admin 4096 Jan 4 15:38 ./test_access
For cases where group part off the permissions is of interest, you could find groups the user belongs to and iterate over them:
for i in $(groups $USER | cut -d':' -f2) ; do find -type d -group "$i" -not -executable ; done
If neither case turns any potential results, the issue could be due to user not belonging to a group which has access to the directory that gives the issue.
Note also that web servers typically use www-data
user/group. You probably want to be checking permissions using that username or group name.
add a comment |
Access to directory is controlled by x
- execute - bit in the permissions. The issue could be due to the user having no executable permissions as owner or a group to which user belongs has no executable permissions set on the directory.
In order to use find
for that task, it's sufficient to specify -user
as the owner of the directory and -not -executable
flags.:
~$ find -type d -user $USER -not -executable
./foo/bar
./test_access
~$ ls -ld ./foo/bar ./test_access
drw-r-xr-- 2 admin admin 4096 Jan 15 03:36 ./foo/bar
drw-r--r-- 2 admin admin 4096 Jan 4 15:38 ./test_access
For cases where group part off the permissions is of interest, you could find groups the user belongs to and iterate over them:
for i in $(groups $USER | cut -d':' -f2) ; do find -type d -group "$i" -not -executable ; done
If neither case turns any potential results, the issue could be due to user not belonging to a group which has access to the directory that gives the issue.
Note also that web servers typically use www-data
user/group. You probably want to be checking permissions using that username or group name.
Access to directory is controlled by x
- execute - bit in the permissions. The issue could be due to the user having no executable permissions as owner or a group to which user belongs has no executable permissions set on the directory.
In order to use find
for that task, it's sufficient to specify -user
as the owner of the directory and -not -executable
flags.:
~$ find -type d -user $USER -not -executable
./foo/bar
./test_access
~$ ls -ld ./foo/bar ./test_access
drw-r-xr-- 2 admin admin 4096 Jan 15 03:36 ./foo/bar
drw-r--r-- 2 admin admin 4096 Jan 4 15:38 ./test_access
For cases where group part off the permissions is of interest, you could find groups the user belongs to and iterate over them:
for i in $(groups $USER | cut -d':' -f2) ; do find -type d -group "$i" -not -executable ; done
If neither case turns any potential results, the issue could be due to user not belonging to a group which has access to the directory that gives the issue.
Note also that web servers typically use www-data
user/group. You probably want to be checking permissions using that username or group name.
answered 7 hours ago
Sergiy KolodyazhnyySergiy Kolodyazhnyy
70.6k9147310
70.6k9147310
add a comment |
add a comment |
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.
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%2faskubuntu.com%2fquestions%2f1109711%2fhow-to-find-files-or-folders-that-are-inaccessible-to-a-certain-user%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