after upgrading my backend to 0.21 I upgraded my frontend to 0.21-40 and changed my minimyth.conf according to the changelog.
Now it stops while booting with the following in /var/log/minimyth*:
error: 'TCode' (or 'MM_DHCP_TCODE') not configured.
error: check '/var/log/minimyth.err.log' for details.
I explicitly configured the MM_DHCP_TCODE option with MM_DHCP_TCODE='Europe/Berlin'
in my minimyth.conf
Sadly, the bug is the result of a purely cosmetic change. I renamed the files that process the configuration file so that the file names match the prefix of the configuration variables they process (e.g. the file '/etc/rc.d/init.d/conf.d/dhcp' was rename '/etc/rc.d/init.d/conf.d/MM_DHCP'). For reasons that I cannot explain, I updated the file names almost everywhere except at least one place. This one place in '/etc/rc.d/init.d/conf' was just below three lines where I did make the change, so I am not sure how I missed it, but I did. As a result, the script was not writing out the processed MM_DHCP variables.
The reason that I renamed the configuration processing files was so that the file names matched the names of the configuration variables that they processed. Having a symbolic link from the old name to the new name and continuing to use the old name in the script would have meant that the script contained the less intuitive old name.lishen2 wrote:Hi , Pablo
Why didn't you just create a symbol link of "dhcp" named MM_DHCP to solve this problem?
Also, changing the name in the script was as easy as creating a symbolic link.