|
|
Line 1: |
Line 1: |
− | Michael, this looks good, but are the instructions complete ?
| |
| | | |
− | I accept the defaults of localhost and root but it cycles back to localhost
| |
− |
| |
− | do I need to change my sme ssh port to 8022
| |
− |
| |
− | do I tell ajaxterm what my ssh port is
| |
− |
| |
− | do you need a signal-event post-upgrade/reboot
| |
− |
| |
− | [[User:Snoble|Snoble]] 05:39, 14 November 2007 (MST)
| |
− |
| |
− | > I accept the defaults of localhost and root but it cycles back to localhost
| |
− |
| |
− | Strange. It works for me on serveral servers. Can you log in another server?
| |
− |
| |
− |
| |
− | > do I need to change my sme ssh port to 8022
| |
− |
| |
− | No. This is the port where the ajaxterm service is listening to.
| |
− |
| |
− | netstat -nlp | grep 8022 should show something like this:
| |
− |
| |
− | tcp 0 0 127.0.0.1:8022 0.0.0.0:* LISTEN 7469/python
| |
− |
| |
− |
| |
− | > do I tell ajaxterm what my ssh port is
| |
− |
| |
− | You can't. Default is 22.
| |
− |
| |
− |
| |
− | > do you need a signal-event post-upgrade/reboot
| |
− |
| |
− | No.
| |
− |
| |
− | --[[User:Mweinber|Mweinber]] 09:36, 14 November 2007 (MST)
| |