I have written a CGI executable. This reads an I/O board and produces pages
with analogue input values that are updated periodically using the meta tag
to refresh the page.
This works well, the target is a TP300 DSP Design PC104 CPU, with 32MB
SDRAM. I am using the tiny tcp stack and slinger.
My problem is that for the last 3 weekends I have left the system running
with a client requesting the pages on an update of 5 seconds. When I return
on the Monday morning the entire system is locked up completely. The only
option I have is to power cycle the target.
I have looked at the CGI executable and it does not allocate any memory
internally, all resources are created on the stack and should therefore be
released when the CGI terminates.
The problem does suggest that the system is running out of resources over
time as if I leave it running over one night it does not lock up.
Are there any known issues with executable CGI’s and slinger that could
explain this ?
Simon Platten, Senior Software Engineer
Bessemer Way, Harfreys Industrial Estate, Great Yarmouth, Norfolk, NR31 0LX.
Tel: (0)1493 668811 Fax: (0)1493 651137
Any views or opinions expressed are solely those of the author and do not
represent those of VT Group, its holding company or any of its subsidiaries