Hi,
On 04/22/2013 07:34 PM, Daniel-Constantin Mierla wrote:
Details about going out can be printed on onsend_route. In this route block, one can execute drop and nothing is sent to the wire. It can be a config started with a special define specified with -A parameter.
Enabling debugger module with cfg trace should give valuable information about what has been executed from config.
From what Andreas suggesting, printing the value of variables as they are assigned is missing, probably can be added by hooking in the interpreter when doing the assignment operation.
Grouping all above under some global/command line parameter can be useful to make it easier to do a dry run.
Alright, thanks, so there seem to be some possibilities to do what I want. I'm going to check the possible options (debugger, onsend-route with drop, passing defines on startup to control the behaviour without changing the config between real operations and dry runs) and will provide some findings and proof of concepts, before digging into developing missing parts.
Andreas