[SOLVED] No way to change ownership from "nobody:users" on shared server?!
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: CentOS 5, Mac OS 10 (Darwin/FreeBSD), Debian, Microsoft Linux
Posts: 14
Rep:
No way to change ownership from "nobody:users" on shared server?!
Hello,
here's my first question, I'll be gentle if you will... +)
So I was trying to remove some files (a sandbox install of joomla 1.5) from a shared hosting environment running FreeBSD 7.3, and ownership perms were set to "nobody:users". So I couldn't touch them. Is there no way around this? I'm afraid I'll have to deal with this again soon, though on a different host (unknown distro).
Tech support changed the perms, and said the only way was for them to do it. I checked the joomla forums and there were a couple thoughts on this, one was with a script, the other was agreed with the above.
Obviously su/sudo doesn't work...
Thanks!
Last edited by macinix; 12-02-2011 at 10:44 PM.
Reason: to mark as solved
Distribution: CentOS 5, Mac OS 10 (Darwin/FreeBSD), Debian, Microsoft Linux
Posts: 14
Original Poster
Rep:
Hi EDDY1,
sorry this wasn't clear from the above:
you CAN'T 'solve' the problem... other than calling your hosting company and having them (recursively) change permissions on the affected directories/files! At least that's what the experts (inc. unSpawn) seem to agree upon as the outcome of the situation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.