in reply to Re^2: System and CGI - File Created but not the Content
in thread System and CGI - File Created but not the Content

Yes it seems that it uses SELINUX

That explains a lot.

Selinux provides "security contexts", and everything that a webserver may run is in the server's security context.

This means that it is not allowed to do a whole lot of things, even if the file permissions allow it.

Which in turn means that virtually everything can go wrong.

I'd recommend to write a daemon that runs a normal user, validates it input and executes the program. The CGI script and the daemon can communicate via TCP or named pipes.

Perl 6 in German

  • Comment on Re^3: System and CGI - File Created but not the Content

Replies are listed 'Best First'.
Re^4: System and CGI - File Created but not the Content
by monkfan (Curate) on Sep 18, 2007 at 12:37 UTC
    ... write a daemon that runs a normal user, validates it input and executes the program. The CGI script and the daemon can communicate via TCP or named pipes.
    How do you do that? Using Perl script? Do you have any example of it?
    Sorry I'm quite new to this, so obvious thing may not be obvious to me.

    Regards,
    Edward
[reply]
      Here is an example how you write a perl script that moves itself into the background (might not work on windows...): 

      !/usr/bin/perl
use strict;
use warnings;

my $ret_val = fork();
if (! defined $ret_val){
    die "Can't fork(): $!";
} elsif ($ret_val == 0){
    # do your daemon tasks here
    sleep 5;
    print "Exiting\n";
} else {
    exit 0;
}

      [download]

      As for the server you should check the Net::Server module.

      Perl 6 in German

[reply]
[d/l]
        Here is an example how you write a perl script that moves itself into the background (might not work on windows...):

        That's OK. The original script almost certainly would.

[reply]

In Section Seekers of Perl Wisdom