New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MS_ERRORFILE does not accept relative path #2853
Comments
Author: dmorissette |
Author: bj
|
Author: dmorissette Note that relative values for MS_ERRORFILE are supported only when set through a CONFIG directive in a mapfile. Setting MS_ERRORFILE through an environment variable still requires an absolute value. Keeping ticket open for docs update |
Author: ejn |
Author: dmorissette Still pending docs update. |
Author: dmorissette |
attachment http://trac.osgeo.org/mapserver/attachment/ticket/2853/ms-svn-patch_msSetErrorFile_relative.patch :
|
Reporter: ben
Date: 2009/01/10 - 03:22
Trac URL: http://trac.osgeo.org/mapserver/ticket/2853
When using CONFIG to set the location for an error log, it is not possible to use a relative path :
Doesn't work:
Works:
This is being reported only because it is inconsistent with other file references in the Mapfile (and took me some time to realise this), which will accept a relative reference (relative to the mapfile).
This is not important (if you know it doesn't accept a relative reference), but vaguely annoying when developing / debugging across different platforms.
Suggestions :
'''Short term''' - Update documentation to make it clear that the reference must be an absolute reference.
'''Longer Term''' - from Daniel Morissette's list response (9 January 2009):
"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."
cheers
Ben
The text was updated successfully, but these errors were encountered: