View Revisions: Issue #4546

Summary 0004546: GLOBAL_POSTFIX not added when OPTIONS is set
Revision 2016-06-01 14:35 by lynX
Description GLOBAL_POSTFIX is not added to the command-line options if a per-service OPTIONS is set. It'd be desireable to either always add GLOBAL_POSTFIX or have a variant of it that is always added.

///

When using GLOBAL_POSTFIX = -l $GNUNET_CACHE_HOME/{}-%Y-%m-%d.log as
suggested by some configurations, only some services write to such
individual logs. Others still gladly send all of their output to the
main log that was provided to gnunet-arm.

https://gnunet.org/bugs/view.php?id=4542#c10785 shows an example of how
the unglobality of GLOBAL_POSTFIX needs to be circumvented.

Revision 2016-06-01 14:32 by lynX
Description When using GLOBAL_POSTFIX = -l $GNUNET_CACHE_HOME/{}-%Y-%m-%d.log as
suggested by some configurations, only some services write to such
individual logs. Others still gladly send all of their output to the
main log that was provided to gnunet-arm.

https://gnunet.org/bugs/view.php?id=4542#c10785 shows an example of how
the unglobality of GLOBAL_POSTFIX needs to be circumvented, and it also
documents the secondary bug of not having $GNUNET_CACHE_HOME available
in other parts of the configuration.

--- tg added this description of the two bugs: ---

GLOBAL_POSTFIX is not added to the command-line options if a per-service OPTIONS is set.
It'd be desireable to either always add GLOBAL_POSTFIX or have a variant of it that is always added.

Also, expansion of variables defined in the [PATH] section does not always work.
It works in the [arm] section in GLOBAL_POSTFIX:

[arm]
GLOBAL_POSTFIX = -l $GNUNET_CACHE_HOME/{}-%F.%T-[].log

But not in other service sections when used in OPTIONS:

[social]
OPTIONS = -L DEBUG -l $GNUNET_CACHE_HOME/{}-%F.%T-[].log
Revision 2016-05-31 22:26 by tg
Description GLOBAL_POSTFIX is not added to the command-line options if a per-service OPTIONS is set.
It'd be desireable to either always add GLOBAL_POSTFIX or have a variant of it that is always added.

--

When using GLOBAL_POSTFIX = -l $GNUNET_CACHE_HOME/{}-%Y-%m-%d.log as
suggested by some configurations, only some services write to such
individual logs. Others still gladly send all of their output to the
main log that was provided to gnunet-arm.

https://gnunet.org/bugs/view.php?id=4542#c10785 shows an example of how
the unglobality of GLOBAL_POSTFIX needs to be circumvented, and it also
documents the secondary bug of not having $GNUNET_CACHE_HOME available
in other parts of the configuration.
Revision 2016-05-31 22:20 by tg
Description GLOBAL_POSTFIX is not added to the command-line options if a per-service OPTIONS is set.
It'd be desireable to either always add GLOBAL_POSTFIX or have a variant of it that is always added.

When using GLOBAL_POSTFIX = -l $GNUNET_CACHE_HOME/{}-%Y-%m-%d.log as
suggested by some configurations, only some services write to such
individual logs. Others still gladly send all of their output to the
main log that was provided to gnunet-arm.

https://gnunet.org/bugs/view.php?id=4542#c10785 shows an example of how
the unglobality of GLOBAL_POSTFIX needs to be circumvented, and it also
documents the secondary bug of not having $GNUNET_CACHE_HOME available
in other parts of the configuration.
Revision 2016-05-31 18:11 by lynX
Description When using GLOBAL_POSTFIX = -l $GNUNET_CACHE_HOME/{}-%Y-%m-%d.log as
suggested by some configurations, only some services write to such
individual logs. Others still gladly send all of their output to the
main log that was provided to gnunet-arm.

13:34 tg sagt: think what i found out is if I set OPTIONS for a service it ignores whatever is in GLOBAL_POSTFIX
13:34 tg sagt: but would have to double check that..
13:34 tg sagt: in /usr/share/gnunet/config.d only a few have OPTIONS, though..
13:35 tg sagt: and this CACHE_HOME thing you can only use in GLOBAL_POSTFIX.. also weird
13:36 tg sagt: anyway, gottarun bbl

https://gnunet.org/bugs/view.php?id=4542#c10785 shows an example of how
the unglobality of GLOBAL_POSTFIX needs to be circumvented, and it also
documents the secondary bug of not having $GNUNET_CACHE_HOME available
in other parts of the configuration.