Line 3: |
Line 3: |
| == smeserver-tftp-server == | | == smeserver-tftp-server == |
| Maintainer: [mailto:smeserver@batley.id.au Trevor Batley]<br> | | Maintainer: [mailto:smeserver@batley.id.au Trevor Batley]<br> |
− | {{ #smeversion: smeserver-tftp-server }} | + | {{#smeversion: smeserver-tftp-server }} |
| | | |
| === Description === | | === Description === |
Line 23: |
Line 23: |
| yum --enablerepo=smecontribs --enablerepo=base install smeserver-tftp-server | | yum --enablerepo=smecontribs --enablerepo=base install smeserver-tftp-server |
| | | |
− | Officially you should then need to apply the database changes etc., but this is not required for this package. | + | 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 post-upgrade |
Line 30: |
Line 30: |
| The tftpd status is controlled via the Thin Clients server-manager panel if you have installed my [[Thinclient|smeserver-thinclient]] contrib. | | The tftpd status is controlled via the Thin Clients server-manager panel if you have installed my [[Thinclient|smeserver-thinclient]] contrib. |
| | | |
− | If you haven't, you'll need to enable the tftp server and expand all the templates etc. | + | If you haven't, you'll need to enable the tftp server |
| config setprop tftpd status enabled | | config setprop tftpd status enabled |
| signal-event tftpd-conf | | signal-event tftpd-conf |
| | | |
| If for any reason the tftp server isn't running, try: | | If for any reason the tftp server isn't running, try: |
− | /etc/init.d/supervise/tftpd restart | + | service tftpd restart |
| | | |
| === Defaults === | | === Defaults === |
Line 81: |
Line 81: |
| | | | | |
| |- | | |- |
− | | refuse* | + | | blksize <sup>1</sup> |
| + | | |
| + | | Value between 512-65464 |
| + | | e.g. equivalent to -B [512-65464] |
| + | |- |
| + | | refuse <sup>2</sup> |
| | | | | |
| | any tftp parameter | | | any tftp parameter |
Line 92: |
Line 97: |
| signal-event tftpd-conf | | signal-event tftpd-conf |
| | | |
− | <nowiki>*</nowiki>refuse does not have a default entry in the configuration database. It can be added as above or removed via | + | <nowiki>*1</nowiki> blksize does not have a default entry in the configuration database. It can be added as above or removed via |
| + | |
| + | see Bug 10646 for updated tftp contrib with addition of default setting |
| + | config delprop tftpd blksize |
| + | signal-event tftpd-conf |
| + | |
| + | <nowiki>*2</nowiki> refuse does not have a default entry in the configuration database. It can be added as above or removed via |
| config delprop tftpd refuse | | config delprop tftpd refuse |
| signal-event tftpd-conf | | signal-event tftpd-conf |
Line 98: |
Line 109: |
| === Uninstall === | | === Uninstall === |
| yum remove smeserver-tftp-server tftp-server | | yum remove smeserver-tftp-server tftp-server |
| + | signal-event post-upgrade ; signal-event reboot |
| | | |
− | Everything should be turned off, but if not, or you just want to make sure
| + | If you want to fully clean up, by removing the entries from the configuration database |
− | /etc/init.d/tftpd stop | + | config delete tftpd |
− | An error saying that /etc/init.d/supervise/tftpd does not exist should be returned
| |
| | | |
| === Source === | | === Source === |