Topic: config tree for checking

[Ken Yap]

It would be nice to have an option to the actions that would create a config tree for checking in a user specified path.
E.g. I do console-save --testdir=fakeroot and afterwards under
fakeroot/ I can find etc/, var/ and so forth and compare against the current setup to see what effect the config change will have. Would also be good for debugging config scripts.

[Charlie Brady]

Ken Yap wrote:

> It would be nice to have an option to the actions that would
> create a config tree for checking in a user specified path.
> E.g. I do console-save --testdir=fakeroot and afterwards under
> fakeroot/ I can find etc/, var/ and so forth and compare
> against the current setup to see what effect the config change
> will have. Would also be good for debugging config scripts.

Such a command argument would make more sense in the "expand-template" command, which we use often during system development. The signal-event command executes action scripts which can perform many actions other than expanding config files, so that I wouldn't recommend using it for debugging on a live system.

Regards

Charlie