Editing Scanco Administration (section)

====Slow/non-responsive computer====

This is usually caused by people logging in via SSH multiple times.  The solution involves resetting the SSH/TCPIP daemon.

:*If you are local at the computer:

You will need to log in as user <code>system</code>.  ONLY EXPERIENCED USERS SHOULD EVER LOG IN AS SYSTEM!

The system will be extremely slow (it will take 5 minutes just to get a log in prompt).  This is expected.

<pre>
$ set host 0   ! user name 'system' and password	
$
$ @sys$startup:tcpip$ssh_shutdown    ! shutdown SSH
$
$ set host 0   ! user name 'system' and password	
$
$ @sys$startup:tcpip$ssh_startup     ! restart SSH
</pre>

Alternatively, you can reboot the system to reset the SSH.  This is not an appropriate solution and it is solving the problem by hitting it with a jack hammer.  Sometimes it is the only choice though.

:*If you are remotely logged in:

You will have to log in as user <code>system</code> and run a script called STOP_START_TCPIP.COM.  

This works essentially the same as for the above method, except that since it would be impossible to restart SSH remotely once it is shut down, two separate scripts are called and submitted on SCEVAL_FAST (make sure the queue isn't clogged) separated by a 1 minute delay. The first script called is STOP_TCPIP.COM and the second is START_TCPIP.COM.

To execute this process, you must log in as system, go to the SYS$SCRATCH directory, and interactively execute the script:
<pre>
$ @STOP_START_TCPIP.COM
</pre>


[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]