Re^3: Opening files to write in browser returns Permission denied

How do you open sitemap.pl in your browser?

You may find it of interest to run this

      my $user = `whoami`;
      chomp $user; 
      my $groups = `groups $user`;
      chomp $groups; 
      print "<br>I am running as $user in groups $groups\n";
[download]

I suspect that the user you get back is not what you expected. I also suspect it is the last 6 in 666 that is fixing your problem. You are setting up a file that anyone can write into. Knowing what groups you are in and the perl process is running you may be able to determine what groups you may have in common. Setting that file (or directory) to be a member of that common group may mean you dont need to let anyone write to that file, but limit it to only userids in that common group.

Comment on Re^3: Opening files to write in browser returns Permission denied Download Code

Replies are listed 'Best First'.
Re^4: Opening files to write in browser returns Permission denied by Lady_Aleena (Priest) on May 05, 2017 at 07:26 UTC
I did as you specified and was surprised by the result. I will have to dig into apache2 to see how can make my "localhost" local to me. Thank you huck! *No matter how hysterical I get, my problems are not time sensitive. So, relax, have a cookie, and a very nice day!* Lady Aleena	[reply]
(OT) Apache process ownership Re^5: Opening files to write in browser returns Permission denied by hippo (Archbishop) on May 05, 2017 at 08:09 UTC
For server-wide apache process ownership see User and Group. For per-vhost user/group assignments see SuexecUserGroup and the suexec tutorial. Make sure you fully understand the implications of using these directives before invoking them on any publicly-accessible server.	[reply]
Re^4: Opening files to write in browser returns Permission denied by Anonymous Monk on May 03, 2017 at 16:33 UTC
Whether it is the first, the second, or the third... That seems to work. P.S. Would it be better to set the file permissions to 777? Why does evil win here?	[reply]