3,704
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 60:
Line 60: + + + + + + + + + + + + + + + + + + + + + Line 120:
Line 141: − pico -w /etc/e-smith/templates-custom/etc/my.cnf/005mysqld + Line 155:
Line 176: − pico -w /etc/e-smith/templates-custom/etc/php.ini/40DataHandling + Line 173:
Line 194: − + − pico S85ErrorPages + − + Line 205:
Line 226: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 322:
Line 394: +
pico -> nano
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 file location, 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.
====/var/service/qpsmtpd/config/peers/0====
The qpsmtpd 'plugins' directives in /etc/e-smith/templates/var/service/qpsmtpd/config/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 update the contents of /var/service/qpsmtpd/config/peers/0.
Note: /var/service/qpsmtpd/config/plugins is not templated at this time.
====/etc/samba/smb.cnf====
/etc/samba/smb.cnf is updated based on the template fragments in /etc/e-smith/templates/etc/smb.cnf
===Specific practical examples===
===Specific practical examples===
cp /etc/e-smith/templates/etc/my.cnf/005mysqld /etc/e-smith/templates-custom/etc/my.cnf/005mysqld
cp /etc/e-smith/templates/etc/my.cnf/005mysqld /etc/e-smith/templates-custom/etc/my.cnf/005mysqld
Edit and make your required additions & changes. This is where you add the changes determined from the mysql documentation.
Edit and make your required additions & changes. This is where you add the changes determined from the mysql documentation.
nano -w /etc/e-smith/templates-custom/etc/my.cnf/005mysqld
Save and exit
Save and exit
Ctrl o
Ctrl o
cp /etc/e-smith/templates/etc/php.ini/40DataHandling /etc/e-smith/templates-custom/etc/php.ini/40DataHandling
cp /etc/e-smith/templates/etc/php.ini/40DataHandling /etc/e-smith/templates-custom/etc/php.ini/40DataHandling
Edit the fragment and make your required changes
Edit the fragment and make your required changes
nano -w /etc/e-smith/templates-custom/etc/php.ini/40DataHandling
Save changes and exit (press the following keys together)
Save changes and exit (press the following keys together)
Ctrl o
Ctrl o
mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
Edit the template fragment with vi or pico
Edit the template fragment with vi or nano
cd /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
cd /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
nano S85ErrorPages
and add the following text
and add the following text
# Add custom error pages here
# Add custom error pages here
ErrorDocument 404 /notfound.html
ErrorDocument 404 /notfound.html
Save & exit from vi or pico
Save & exit from vi or nano
Ctrl c
Ctrl c
Ctrl x
Ctrl x
A full list of error codes can be found at http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
A full list of error codes can be found at http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
====smb.conf====
This example comes from a forum post at http://forums.contribs.org/index.php/topic,49238.0.html where a user asks how to enable domain login to SME8 server from Windows 98 workstations,
and is based on advice from http://ubuntuforums.org/showthread.php?t=1617097
The SME server template fragments were examined & it was determined that the most suitable for the requirement was /etc/e-smith/templates/etc/smb.conf/11lanmanPasswords
Make a custom template folder
cp /etc/e-smith/templates/etc/smb.conf/11lanmanPasswords /etc/e-smith/custom-templates/etc/smb.conf/
Edit the template fragment with vi, nano or nano
cd /etc/e-smith/custom-templates/etc/smb.conf
nano 11lanmanPasswords
and change the contents to the following code (in this example the perl code shown will allow parameters to be controlled by db commands rather than hard coding the parameters as text into the fragment)
{
$OUT .= "lanman auth = $smb{'LanManPasswords'}\n" if $smb{'LanManPasswords'};
$OUT .= "client lanman auth = $smb{'ClientLanManPasswords'}\n" if $smb{'ClientLanManPasswords'};
$OUT .= "client plaintext auth = $smb{'ClientPlaintextPasswords'}\n" if $smb{'ClientPlaintextPasswords'};
}
Save & exit from nano
Ctrl c
Ctrl x
Then check & note current settings
config show smb
Then issue
config setprop smb LanManPasswords yes
config setprop smb ClientLanManPasswords yes
config setprop smb ClientPlaintextPasswords yes
Expand template & restart service (both included in the one signal-event command)
signal-event workgroup-update
Then review settings
config show smb
Then manually check /etc/samba/smb.conf to see all changes & settings are present eg
cat /etc/samba/smb.conf
Additional steps are required to modify passwords for Windows 98 users, from this post http://ubuntuforums.org/showthread.php?t=1617097
Re input passwords for every Windows 98 user (where username is the sme user who is logging into any Windows 98 workstation)
smbpasswd -a username
Then every Windows 98 user should log out and then log in again on their Windows 98 workstations (to pick up the changes on the server & allow successful login)
----
----
[[Category:Howto]]
[[Category:Howto]]
[[Category:Developer]]
