IIRC, LOG only logs some info on the mapserv request status at the end of its execution. I don't use it much and don't know much about it.If there is something definitively "bad" about modern Mapserver it is the migration of configuration directives into "magic string" blocks of the map file, which are much less well documented that the "official" elements of the file.
To get debugging output, with MapServer 5.0+, set:
CONFIG "MS_ERRORFILE" "/var/tmp/ms.log"
... and then set DEBUG level (ON, or number between 1 and 5) at the top-level in the mapfile and in each layer for which you want debugging output.
More details are available in RFC-28: http://mapserver.gis.umn.edu/development/rfc/ms-rfc-28
CONFIG, PROCESSING, METADATA, that's right, I'm looking at you.
2 comments:
I've been going on about this all the years you were away from editors and compilers. See this post for example.
I've been complaining about PROCESSING, CONFIG, and METADATA too for quite a while. They're our back door into free-form syntax because we're too hesitant to add real directives to the mapfile syntax. Either the mapfile syntax is too rigid and we should use hash keys like PROCESSING, CONFIG and METADATA for everything, or we should add real directives for new functionality.
The situation we're in now is the worst of both worlds. Pretty much all of the new stuff that's been added in the past couple of years has been tacked on into the hash keys -oriented syntax.
Post a Comment