Skip to content

4.8. Probing the configuration

John edited this page Dec 25, 2015 · 3 revisions

Once the configuration files are prepared, the ebus daemon should be called with the "--checkconfig" option in order to check the configuration files for validity. With this option, ebusd will not fork into background and not open any device or network port, but only probe the files, print out problems to stdout and terminate.

When also using the "--scanconfig" option for automatic configuration, ebusd also accepts scan message data as additional arguments on the command line for checking a particular scan configuration, e.g. "FF08070400/0AB5454850303003277201".

In addition to that, when using the "--dumpconfig" option the daemon will check the configuration files and on success print all message definitions in CSV configuration file format with all templates resolved to the final value.