Ben,
You are correct that relative paths are not supported for MS_ERRORFILE.
You could file a ticket about this, and if/when time permits we'll look
at the implications of supporting relative paths in all possible
scenarios and see if this could safely be added. i.e. it may be possible
to get predictable results with a relative path only when setting
MS_ERRORFILE in the mapfile but not when setting it via an environment
variable, we'll have to see.
Daniel
Ben Madin wrote:
G'day all,
as a negative, Can you not use a relative reference for the errorfile?
for example, using :
CONFIG "MS_ERRORFILE"
"/Users/19022662/Sites/marketprices/mapserver/mserr.log"
DEBUG 4
works as expected, writing copious quantities to the log.
using :
CONFIG "MS_ERRORFILE" "mserr.log"
DEBUG 4
does not, although both the .log file and the .map file are in the
/Users/19022662/Sites/marketprices/mapserver/ directory. Relative paths
work fine for symbol files, data etc.
I also note that the RFC28 refers to setting this :
It will be possible to specify MS_ERRORFILE either as an environment
variable or via a CONFIG directive inside a mapfile:
CONFIG "MS_ERRORFILE" "/tmp/mapserver.log"
or
CONFIG "MS_ERRORFILE" "stderr"
but doesn't specify whether or not a relative path could be used.
This is inconsistent with all other specifications of path, can/should
it be amended? Should I file this as a bug?
cheers
Ben
--
Daniel Morissette
http://www.mapgears.com/
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
