Hi, This is repost of Problem with for in CGI with more comments and explaining (it looks like on prev post problems was not so clear for understanding as I thought ;( ). So problem :
I wonna to start some long-running code from web-interface. This can be done 2 ways :
- spawn separate process with help of fork
- use at or cron
Fork looks like more lazy (and right!) way to do this thing.
Unofrtunately my process works fine in command line, but stoped mystically in Apache (after about 10 mins of work)
Code looks like :

redirect_to("Prev_page.html") if fork();
#child here
close STDIN; close STDERR; close STDOUT;
# we inherit this filehandles from Apache. If we don't close, Apache w
+ill wait for child
use POSIX 'setsid';
setsid;
#Change PGID. So Apache can't kill child (and won't know about it)
# Long-running code here
[download]

Similar running program on the same server works without any problem (about 20 mins of execution).
Apache works under SuEXEC. No ulimits setted (checked both in CGI script and in shell for this user).

Can anybody imagine reason why this can happens ?
Sincerely, Nikita Savin

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.