|
|
Line 1: |
Line 1: |
− | IMHO the first two steps of the procedure are not necessary as the configuration database value is used to alter the port. After changing this port the custom template has no additional value - [[User:Cactus|Cactus]] 04:49, 21 March 2007 (EDT)
| |
− |
| |
− |
| |
− | And instead of expanding templates and restarting services just signal-event, i think ...
| |
− | signal-event remote-access
| |
− | [[User:Snoble|Snoble]] 19:37, 21 March 2007 (EDT)
| |
− |
| |
− | Corrected. --[[User:PicsOne|PicsOne]] 03:57, 1 April 2007 (EDT)
| |
− |
| |
− | == Templates and services ==
| |
− |
| |
− |
| |
− | Hi mmccan, and thanks for your corrections.
| |
− |
| |
− | Viewing under signal-event remoteaccess-update I see there is not necesary to restart sshd service.
| |
− |
| |
− | Then this is the final commands
| |
− |
| |
− | config setprop sshd TCPPort <newport>
| |
− | signal-event remoteaccess-update
| |
− |
| |
− | without
| |
− |
| |
− | /etc/init.d/sshd restart
| |
| | | |
| Can you confirm? | | Can you confirm? |
| | | |
− | --[[User:PicsOne|PicsOne]] 17:01, 13 April 2007 (EDT)
| + | confirmed, also [[Bugzilla:2382]] which will make this howto redundant |
− | | |
− | ----
| |
Revision as of 01:42, 14 April 2007
Can you confirm?
confirmed, also Bugzilla:2382 which will make this howto redundant