Just discovered that, unfortunately, the solution is a bit more complicated:
- The file /etc/nsswitch.conf is overwritten each time an update is performed and the post-upgrade event is signaled.
- If the inclusion of wins in the name resolution shall persist updates, a custom template for the nsswitch.conf file must be created, so that the actual nsswitch.conf file is recreated in the intended way during each update. (Simply editing the template will not be sufficient since the tamplates may be updated from time to time with new default versions -- according the manual).
- Create a new directory nsswitch.conf for the template in the template custom branch at
/etc/e-smith/templates-custom/etc/- Copy the template file
/etc/e-smith/templates/etc/nsswitch.conf/10files to the CUSTOM branch's new directory
/etc/e-smith/templates-custom/etc/nsswitch.conf/- Edit the newly copied custom template
/etc/e-smith/templates-custom/etc/nsswitch.conf/10files:
change the line
hosts: { ($AccessType eq "off") ? "files" : "files dns" }to
hosts: { ($AccessType eq "off") ? "files" : "files dns wins" }- Use
signal-event post-upgrade and
signal-event reboot to have the new custom template rewrite the nsswitch.conf
This solution seems to work (for now...
), but I am not at all familiar with the sme-server's template and database system, so please correct the above if necessary.