371
edits
Changes
Jump to navigation
Jump to search
Line 21:
Line 21: − + + + + + + Line 32:
Line 37: − − Officially you should then need to apply the database changes etc. Whilst this is not required to be able to run the tftp server straight away, it will be required at some stage, and the server manager will remind you to, until you do. − − signal-event post-upgrade − signal-event reboot Line 45:
Line 45: − service tftp restart +
use systemctl rather than service (for restart)
/tftpboot/ *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/tftpboot/ *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
<syntaxhighlight lang="bash">
mkdir -p /etc/e-smith/templates-custom/etc/exports/
echo "/tftpboot/ *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)" > /etc/e-smith/templates-custom/etc/exports/30tftp
expand-template /etc/exports
</syntaxhighlight>
/tftpboot/images/ubunturescue_1104/ *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/tftpboot/images/ubunturescue_1104/ *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
if you have installed smeserver-nfs
=== Installation ===
=== Installation ===
yum --enablerepo=smecontribs --enablerepo=base install smeserver-tftp-server
yum --enablerepo=smecontribs --enablerepo=base install smeserver-tftp-server
The tftp status can be controlled via the Thin Clients server-manager panel if you have installed my [[Thinclient|smeserver-thinclient]] contrib.
The tftp status can be controlled via the Thin Clients server-manager panel if you have installed my [[Thinclient|smeserver-thinclient]] contrib.
If for any reason the tftp server isn't running, try:
If for any reason the tftp server isn't running, try:
systemctl restart tftp
=== Defaults ===
=== Defaults ===