Hi Yavor,
We have not head of any other reports of core dumps. It's hard to
imagine that the nosetpage switch issue would have anything to do with
core dumps.
To answer your question about
/cgi-bin/webwork/system/cgi/cgi-scripts/ vs
/cgi-bin/webwork/system/cgi/ . First if you follow the setup
instructions, everything should be set correctly. If this is not set
correctly, nothing will work so that shouldn't be the source of your
problems. It seems strange to me that you are getting core dumps in
/cgi-bin/webwork/system/cgi/ since unless you are debugging, that
directory should be bypassed by WeBWorK.
Now for the answer. The shell scripts are only used for debugging
but WeBWorK normally automatically bypasses them. Look at
.../webwork/system/lib/webworkConfig.pm which is created by the setup
process. You will see the 2 lines:
(1) $cgiWebworkURL = "/cgi-bin/webwork/system/";
(this may be different depending on how you set things up). But no
matter how you set up your system, this is supposed to point to (look
at Apache's config file) .../webwork/system/cgi/ which is where the
shell scripts reside. However, the next line reads:
(2) $cgiWebworkURL .= "cgi-scripts/" unless $cgiDebugMode; (which means append cgi-scripts/ to the path).
Thus unless $cgiDebugMode is set to 1 (by default it's set to 0),
the shell scrips are bypassed since $cgiWebworkURL =
"/cgi-bin/webwork/system/cgi-scripts/";
Arnie
<| Post or View Comments |>
|