Hey all you *nix wizards out there! I feel really stoopid (er, uh shall we say embarrassed?) to send this one to tech support but my experimenting with PHP scripts (Yea! http://www.hotscripts.com) has left me with a little “dreamhost specific” problem.
Certain of my “test” installations have left files owned by “nobody” scattered in places within my directory tree. Granted, some of them were probably created before the move to DH2 and got moved “as they were found”(didn’t DH1 run scripts as nobody?), but not all, and the way DH2 runs scripts as “youruser” complicates the problem:
I’ve found the common “nobody.cgi” and another script called “delete.pl” that let you manipulate (to varying degrees) “nobody’s” files on your server (yep, even above your “public_html” dir!), but since DH2 runs your scripts as your user, they will not work for their intended purpose, which is to allow deletion of “nobody”'s files. Back to the same situation you have working from the command line in the shell.
Even stranger, after running a test installation of a PHP site management script called “administr8”, I even found files created by the script that are owned by user “dhapache”…(This is a new one on me!) …looks like I’ve got the same “unable to delete/edit/etc.” problem with these puppies.
It seems that a user ought to be able to delete such files if they are in directories the user owns, but for the life of me I can’t figure out how.
This is the third night I have dug around in all my *nix books till “zero_dark_thirty” in the morning trying to figure out a way to delete such files without pestering the sysadmin, but I’m whipped. I’m just not finding a way around this.
Digging around in the apache documentation even made it worse (kinda overloaded my brain) when I got to the su-exec stuff, and the various ways you can configure CGI access…at least I learned a little, and I think I have a better understanding of (and appreciation for) how/why DH does it the way they do…but I would still like to be able to kill such files without having to bus support whenever I am done with an installation.
Anybody have any suggestions?
(address witheld out of sheepishness and shame - I’m really gonna feel silly if this turns out to be “really easy”)