In a terminal, type man audit2allow to learn how you can extend your SELinux policy.
| [reply]
[d/l] |
| [reply] |
Aha, mhm, interesting. "i turnedoff SELinux... eventhough its not working in browser" - does that mean that the problem persists even with SELinux turned off? If so, what could we conclude from that fact?
See, we aren't a perl helpdesk, even if we resemble one - we just help each other. To help you, you have to help us helping you, which means you providing us with as much information as necessary and as little information as possible to draw the picture.
I suggested extending SELinux policy - turns out that this has no effect. But - did you even do that? Nothing about that in your post.
I'm not inclined to play guessing. See I know what I mean. Why don't you?
To enable us to help you, post your code, post error messages, i.e. relevant excerpts from /var/log/messages and the web server's error log (for F11, that's /var/log/httpd/error_log)
| [reply]
[d/l]
[select] |
run your CGI script as your web server user with something like:
su -l www -c "/usr/bin/perl /path/to/script/script.pl"
Presuming www is the user running your web server, and your perl binary is in /usr/bin, adjust if not | [reply]
[d/l] |