in reply to External C ran from External Perl ran from CGI
This seems to come up a lot. Usually, it happens because when you run it "locally", your personal user account has permission to read, write and/or execute particular files in cited directories, whereas when it runs via a web server, the web server's user account (usually "nobody") does not have the same permission. Check permissions on the various directories and files involved.
update: This chdir works, but does the change in dir crash the program?
If this were part of the problem, it most likely would have failed when you ran it "locally".
the first program is run from a fork deliberately created by perl, because it is run twice, in parallel. there is no deliberate fork for the second as it runs once on it's own. should this be the case?
I suppose it might depend on what these programs are supposed to be doing. Could there be a problem involving resources that should be locked (to avoid concurrent access), but aren't?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: External C ran from External Perl ran from CGI
by seaver (Pilgrim) on May 19, 2003 at 17:05 UTC | |
|
Re: Re: External C ran from External Perl ran from CGI
by seaver (Pilgrim) on May 16, 2003 at 20:04 UTC |