[Ipsec-tools-commits] [ ipsec-tools-Bugs-1587518 ] Nice to have: log environment variables

[SourceForge.net <no...@so...>]

Bugs item #1587518, was opened at 2006-10-30 14:36
Message generated for change (Comment added) made by sundialservices
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=541482&aid=1587518&group_id=74601

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: CVS snapshot
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mike Robinson (sundialservices)
Assigned to: Nobody/Anonymous (nobody)
Summary: Nice to have: log environment variables

Initial Comment:
It would greatly simplify debugging if the 
debug-level output included the values that are being 
assigned to environment-variables.

It's a trivial change to "isakmp_cfg.c" of course.

Likewise to report if the script failed.  (I don't 
see that.)

While "troubleshooting a startup or shutdown script" 
is something that we ALL want to "just do once, and 
then fuhgeddaboudit," this simple change makes the 
work much easier.

----------------------------------------------------------------------

>Comment By: Mike Robinson (sundialservices)
Date: 2006-10-30 15:04

Message:
Logged In: YES 
user_id=854356

In general, I found it difficult to easily determine how and when a 
script was executed, and with what variables.  For a bit, also, the 
fact that "mode_cfg" defers execution of a phase1_up script threw me.  
Minor-looking improvements to these debug messages really make this 
much easier to figure out.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=541482&aid=1587518&group_id=74601