688
edits
Changes
From SME Server
Jump to navigationJump to searchNote about qpsmtpd/config/plugins and templates.metadata
If the template you have copied includes perl code, you will need to write the appropriate perl code to create your new output, or place your text changes after the final closing brace ("}") of the perl commands.
If the template you have copied includes perl code, you will need to write the appropriate perl code to create your new output, or place your text changes after the final closing brace ("}") of the perl commands.
===templates.metadata===
Template output, ownership, and other metadata can also be controlled by configuration settings stored under /etc/e-smith/templates.metadata.
While the default output location for most templated config files matches the path to the collection of template fragements, it is also possible to specify a different output filename using an entry within the /etc/e-smith/templates.metadata folder.
Specifically, the qpsmtpd 'plugins' directives in /etc/e-smith/templates/var/service/qpsmtpd/plugins do NOT affect the content of /var/service/qpsmtpd/plugins as expected.
Instead, due to this line in /etc/e-smith/'''templates.metadata'''/var/service/qpsmtpd/config/plugins:
OUTPUT_FILENAME="/var/service/qpsmtpd/config/peers/0"
This command:
expand-template /var/service/qpsmtpd/config/plugins
Will actually updates the contents of /var/service/qpsmtpd/config/peers/0.
===Specific practical examples===
===Specific practical examples===
