Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Subst variables and Execute, posted by soren poulsen on Wed Jul 21 16:26:17 2010 
    icon2.gif   Re: Subst variables and Execute, posted by Stefan Ritt on Wed Jul 21 16:38:05 2010 
       icon2.gif   Re: Subst variables and Execute, posted by soren poulsen on Thu Jul 22 10:17:29 2010 
          icon2.gif   Re: Subst variables and Execute, posted by soren poulsen on Mon Jul 26 11:41:44 2010 
             icon2.gif   Re: Subst variables and Execute, posted by Stefan Ritt on Wed Jul 28 17:08:55 2010 
                icon2.gif   Re: Subst variables and Execute, posted by soren poulsen on Thu Jul 29 13:45:47 2010 
Message ID: 66871     Entry time: Thu Jul 29 13:45:47 2010     In reply to: 66865
Icon: Reply  Author: soren poulsen  Author Email: soren.poulsen@cern.ch 
Category: Question  OS: Linux  ELOG Version: 2.7.8 
Subject: Re: Subst variables and Execute 

Stefan Ritt wrote:

soren poulsen wrote:

There is sometimes a problem with substitutions like "Execute delete = echo $message id".

It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.

In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.

Soren

I tried to reproduce it, but it always worked for me. So I need a step-by-step instruction from you on how to reproduce the problem, ideally starting from the demo logbook from the distribution. Only if I can reproduce the problem, I will be able to fix it. 

 It is of course my job to reproduce it (and explain how-to).  Thanks for your consideration.

ELOG V3.1.5-3fb85fa6