Changes

From SME Server
Jump to navigationJump to search
707 bytes added ,  10:45, 20 November 2018
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 58: Line 58:  
| log
 
| log
 
| normal
 
| normal
| normal/verbose
+
| normal/verbose/disabled
| equivalent to -v or -vv
+
| equivalent to -v or -vv or none
 
|-
 
|-
 
| user
 
| user
| root
+
| nobody
| root/nobody
+
| nobody/<user>
| should default to nobody, but this doesn't work
+
| default to nobody, any valid user id
 
|-
 
|-
 
| privilege
 
| privilege
 
| ro
 
| ro
 
| ro/rw
 
| ro/rw
| read only or read-write
+
| read-only or read-write (rw equivalent to -c)
 
|-
 
|-
 
| timeout
 
| timeout
Line 80: Line 80:  
| any directory
 
| any directory
 
|
 
|
 +
|-
 +
| blksize <sup>1</sup>
 +
|
 +
| Value between 512-65464
 +
| e.g. equivalent to -B [512-65464]
 +
|-
 +
| refuse <sup>2</sup>
 +
|
 +
| any tftp parameter
 +
| e.g. blksize equivalent to  -r blksize
 
|-
 
|-
 
|}
 
|}
Line 85: Line 95:  
These settings can be set/changed via
 
These settings can be set/changed via
 
  config setprop tftpd <prop> <value>
 
  config setprop tftpd <prop> <value>
 +
signal-event tftpd-conf
 +
 +
<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
 
  signal-event tftpd-conf
 
  signal-event tftpd-conf
    
=== 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 ===

Navigation menu