Gossamer Forum
Home : General : Perl Programming :

Scripts generated files as 'nobody'

Quote Reply
Scripts generated files as 'nobody'
Anyone got a work around this? All of the files created by my scripts are set as 'nobody'. This is a real pain cos i dont have high enough access to upload/chmod/edit etc them. At the moment I am using a web-based editor to do the job, but this is a real pain. Anyone know of a shortcut (tried CHOWn, but i dont have permission to run CHOWn, thus i cant change the owner to myself Frown). I was wondering how all the other hosts that I used to have manged to do it where the files created were owned by you, rather than 'nobody'.

Any feedback would be appreciated Smile


Andy (mod)
andy@ultranerds.co.uk
Want to give me something back for my help? Please see my Amazon Wish List
GLinks ULTRA Package | GLinks ULTRA Package PRO
Links SQL Plugins | Website Design and SEO | UltraNerds | ULTRAGLobals Plugin | Pre-Made Template Sets | FREE GLinks Plugins!
Quote Reply
Re: [AndyNewby] Scripts generated files as 'nobody' In reply to
Well, it's making the files owned by 'nobody' because that's what the httpd is being run as. If you don't have root access, I don't think there's anything you can do about it. If you do have root access, then you can consider getting suEXEC (http://httpd.apache.org/docs/suexec.html) working.
Quote:
What is suEXEC?

The suEXEC feature -- introduced in Apache 1.2 -- provides Apache users the ability to run CGI and SSI programs under user IDs different from the user ID of the calling
web-server. Normally, when a CGI or SSI program executes, it runs as the same user who is running the web server.

Used properly, this feature can reduce considerably the security risks involved with allowing users to develop and run private CGI or SSI programs. However, if suEXEC is
improperly configured, it can cause any number of problems and possibly create new holes in your computer's security. If you aren't familiar with managing setuid root programs
and the security issues they present, we highly recommend that you not consider using suEXEC.


Adrian