Well, I've tried debugging Mapserver to figure this out and have learned a couple of things...but I still haven't solved the problem re: why these tmp files are suddenly appearing in the /tmp directory.
I thought perhaps that some debugging had gotten turned on somewhere to cause those files to appear now, but learned, as I stepped through mapcontext.c and maphttp.c that the context file is always written out in this process. It's simply the "caching" location that dictates where. So, I went looking around and determined that up until 2 weeks ago, these files were being written to a directory called "ogc_tmp". That directory is the one we point to with the IMAGEPATH/IMAGEURL parameters included in the imagepath.inc.map file pointed to with this line in the wmsContextServer map file: INCLUDE "../../../mapserv/conf/imagepath.inc.map" Its contents are: IMAGEPATH "/data/nl18/httpd/htdocs/ogc_tmp/" IMAGEURL "/ogc_tmp/" I thought, perhaps, that all of sudden maybe the directory had changed or something so now Mapserver couldn't find it from the location its defined at in the mapfile, but when I cd into the directory that contains the wmsContextServer.map file, I can do a directory listing of "/data/nl18/httpd/htdocs/ogc_tmp/" and see the contents of the directory. I went to the location of the Mapserver executable in /cgi-bin and did the same and can see the directory from there also. But, am I on the right track here? All the other temporary files continue to be sent to the /ogc_tmp/ directory (image files, for example). It's only the contexts that are being placed in the /tmp directory now. So, besides this IMAGEPATH setting (which doesn't appear to have changed any, either in the wmsContextServer.map file or in the environment itself), is there some other place that that ogc_tmp directory might be getting specified? And when Mapserver is unable to find whatever place that other place is telling it to find /ogc_tmp it's defaulting to /tmp? Would Mapserver do that...default to /tmp if it can't find a specified location for something? I've been comparing source-controlled map files for days now trying to find what's changed and is causing these files to suddenly appear in this new location. If anyone can think of ANYTHING that might point me somewhere useful, I would certainly appreciate it. cheers, jtm -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Mapserver-tmp-files-appearing-all-of-a-sudden-w-CONTEXT-parameter-used-tp7009495p7026365.html Sent from the Mapserver - User mailing list archive at Nabble.com. _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
