[Sguil-devel] Sguild Logging

[Dave Crawford]

Greetings,

Is there a specific reason why the command line value passed for setting the log directory ( -L ) is explicitly overwritten with a hardcoded location?


Line 194:

-L { set state log_dir }

Line 213:

log_dir { set LOG_DIR $arg; set state flag }


Then finally:

Line 223 of sguild:

set LOG_PATH /var/log/sguild


-Dave

[Bamm Visscher]

I assume you are looking at CVS. I am working at adding improved
logging, but it is far from finished. You will see various states of
functionality in CVS until I release the final version.

Thanks for the report!

Bamm

Post by Dave Crawford
Greetings,
Is there a specific reason why the command line value passed for setting the
log directory ( -L ) is explicitly overwritten with a hardcoded location?
-L { set state log_dir }
log_dir { set LOG_DIR $arg; set state flag }
set LOG_PATH /var/log/sguild
-Dave
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Sguil-devel mailing list
https://lists.sourceforge.net/lists/listinfo/sguil-devel