P
Public Interest
I got shell access, but not cronjob access. I want to use a CGI to start the
job, and use either a html refresh or a task in windows as the cronjob
starter.
In fact, I can even use cgi to change the refresh rate according to
conditions set in perl script.
My only problem is my JOB takes too much time to run: Job A takes10 minutes,
Job B takes 2-8 hours. The problem with CGI is that cgi has a lifetime of
180 seconds or so and it will be broken after that time. Here is what I want
to do:
Part1 Start a process which is then indepentant of the CGI, so even the CGI
is dead or finished, the new process is still running. Should I start a
child, a sys, an exec
Part2 Print running logs to a output file, and the output can be seen from
web. Part2 is easy, but if I want to print the file into an absolute dir,
should I use the absolute dir of webspace under apache or abs dir under
shell? such as which to call dir1/dir3/html/ from dir1/dir2/cgi-bin/?
html,
/html,
.../dir3/html
/dir1/dir2/html
job, and use either a html refresh or a task in windows as the cronjob
starter.
In fact, I can even use cgi to change the refresh rate according to
conditions set in perl script.
My only problem is my JOB takes too much time to run: Job A takes10 minutes,
Job B takes 2-8 hours. The problem with CGI is that cgi has a lifetime of
180 seconds or so and it will be broken after that time. Here is what I want
to do:
Part1 Start a process which is then indepentant of the CGI, so even the CGI
is dead or finished, the new process is still running. Should I start a
child, a sys, an exec
Part2 Print running logs to a output file, and the output can be seen from
web. Part2 is easy, but if I want to print the file into an absolute dir,
should I use the absolute dir of webspace under apache or abs dir under
shell? such as which to call dir1/dir3/html/ from dir1/dir2/cgi-bin/?
html,
/html,
.../dir3/html
/dir1/dir2/html