[GRASS-user] Different GIS_ERROR_LOG files for different instances of GRASS?

Hi

I am running simulations which are using GRASS for some calculations,
and I would like to use GIS_ERROR_LOG as a log file. How can I have
different GIS_ERROR_LOG for different instances of GRASS, so that each
instance has it's own log file?

Thanks

Rainer

--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Faculty of Science
Natural Sciences Building
Private Bag X1
University of Stellenbosch
Matieland 7602
South Africa

On Tue, Oct 7, 2008 at 5:45 PM, Rainer M Krug <r.m.krug@gmail.com> wrote:

Hi

I am running simulations which are using GRASS for some calculations,
and I would like to use GIS_ERROR_LOG as a log file. How can I have
different GIS_ERROR_LOG for different instances of GRASS, so that each
instance has it's own log file?

Best might be to change the name "GIS_ERROR_LOG" which is defined in
lib/gis/error.c

into a variable.
?

Markus

Markus Neteler wrote:

> I am running simulations which are using GRASS for some calculations,
> and I would like to use GIS_ERROR_LOG as a log file. How can I have
> different GIS_ERROR_LOG for different instances of GRASS, so that each
> instance has it's own log file?

Best might be to change the name "GIS_ERROR_LOG" which is defined in
lib/gis/error.c

into a variable.
?

Done in 7.0 (r33740).

If set, $GIS_ERROR_LOG should be the absolute path to the log file (a
relative path will be interpreted relative to the process' cwd, not
the cwd at the point you set the variable). If not set,
$HOME/GIS_ERROR_LOG is used instead.

The previous behaviour of writing to both $HOME/GIS_ERROR_LOG and
$GISBASE/GIS_ERROR_LOG has been eliminated; only one log file will be
written.

As before, the file will only be used if it already exists.

Also, the current directory is obtained using getcwd() rather than
popen("pwd"), so it should work on Windows.

--
Glynn Clements <glynn@gclements.plus.com>

Rainer Krug wrote:

I am running simulations which are using GRASS for some calculations,
and I would like to use GIS_ERROR_LOG as a log file. How can I have
different GIS_ERROR_LOG for different instances of GRASS, so that each
instance has it's own log file?

using the existing grass 6 code you'd have to run each instance as a
different user.

see the end of:
  http://grass.osgeo.org/grass64/manuals/html64_user/variables.html

Hamish

Hamish wrote:

> I am running simulations which are using GRASS for some calculations,
> and I would like to use GIS_ERROR_LOG as a log file. How can I have
> different GIS_ERROR_LOG for different instances of GRASS, so that each
> instance has it's own log file?

using the existing grass 6 code you'd have to run each instance as a
different user.

see the end of:
  http://grass.osgeo.org/grass64/manuals/html64_user/variables.html

Changing HOME will be sufficient to change the location of the file,
but that will also affect anything else which is accessed via $HOME,
e.g. ~/.Xauthority, ~/.bashrc, etc.

--
Glynn Clements <glynn@gclements.plus.com>

On Wed, Oct 8, 2008 at 12:53 AM, Glynn Clements
<glynn@gclements.plus.com> wrote:

Markus Neteler wrote:

> I am running simulations which are using GRASS for some calculations,
> and I would like to use GIS_ERROR_LOG as a log file. How can I have
> different GIS_ERROR_LOG for different instances of GRASS, so that each
> instance has it's own log file?

Best might be to change the name "GIS_ERROR_LOG" which is defined in
lib/gis/error.c

into a variable.
?

Done in 7.0 (r33740).

Backported to 6.4.svn: r33753

If set, $GIS_ERROR_LOG should be the absolute path to the log file (a
relative path will be interpreted relative to the process' cwd, not
the cwd at the point you set the variable). If not set,
$HOME/GIS_ERROR_LOG is used instead.

ok

The previous behaviour of writing to both $HOME/GIS_ERROR_LOG and
$GISBASE/GIS_ERROR_LOG has been eliminated; only one log file will be
written.

That's not entirely clear to me. Say, lib/init/variables.html may need a fix
for that.

As before, the file will only be used if it already exists.

Also, the current directory is obtained using getcwd() rather than
popen("pwd"), so it should work on Windows.

Perfect, thanks.

Markus

These are more and more reasons, to use 6.4 instead.

Thanks a million for all your suggestions,

Rainer

On Wed, Oct 8, 2008 at 10:34 AM, Markus Neteler <neteler@osgeo.org> wrote:

On Wed, Oct 8, 2008 at 12:53 AM, Glynn Clements
<glynn@gclements.plus.com> wrote:

Markus Neteler wrote:

> I am running simulations which are using GRASS for some calculations,
> and I would like to use GIS_ERROR_LOG as a log file. How can I have
> different GIS_ERROR_LOG for different instances of GRASS, so that each
> instance has it's own log file?

Best might be to change the name "GIS_ERROR_LOG" which is defined in
lib/gis/error.c

into a variable.
?

Done in 7.0 (r33740).

Backported to 6.4.svn: r33753

If set, $GIS_ERROR_LOG should be the absolute path to the log file (a
relative path will be interpreted relative to the process' cwd, not
the cwd at the point you set the variable). If not set,
$HOME/GIS_ERROR_LOG is used instead.

ok

The previous behaviour of writing to both $HOME/GIS_ERROR_LOG and
$GISBASE/GIS_ERROR_LOG has been eliminated; only one log file will be
written.

That's not entirely clear to me. Say, lib/init/variables.html may need a fix
for that.

As before, the file will only be used if it already exists.

Also, the current directory is obtained using getcwd() rather than
popen("pwd"), so it should work on Windows.

Perfect, thanks.

Markus

--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Faculty of Science
Natural Sciences Building
Private Bag X1
University of Stellenbosch
Matieland 7602
South Africa