Quickdata Quikstop-15 Spezifikationen PDF herunterladen (Seite 45)

Page 40 of 54

6. Abnormal procedures

Most system malfunctions and advisory conditions are programmed into TOAD.

You will be presented with a diagnostic message along with a recommended

remedial action to resolve the conflict. Please follow the on screen instructions

in the event of such a failure.

Consult with the DA or observatory staff if you’re not sure what to do.

6.1. Restarting TCS

If TCS is hanging, or starting to behave very sluggishly, a restart of TCS can be

indicated:

• If possible, press the EXIT button in TCS and wait for the TCS window to

disappear.

• If TCS is hung:

o bring forward the blue bigrock terminal that started TCS (hidden

behind the TCS window)

o press <ctrl>-c to kill TCS

• Make sure all TCS related processes have ended by executing the

command killtcs repeatedly until killtcs does not report any processes

left. If some processes are hung stubbornly, you may have to manually

force kill them by executing a kill -9 PID, where PID is the process ID

number shown during the killtcs command.

• Restart TCS by issuing the command tcs

6.2. Restarting MOPS

• If possible, attempt to quit MOPS by pressing the QUIT button on the

lower right of the MOPS GUI.

• If that is not possible, switch to the green terminal window behind the

MOPS window which started MOPS and press <ctrl>-c to kill MOPS

• Execute the command killmops repeatedly until no more processes are

found.

• If some processes are stubbornly refusing to go away, you may have to

manually force kill them by issuing a kill -9 PID command, where PID

is the process ID that is displayed by the killmops command.

• start MOPS by executing the command mops.

1 2 ... 40 41 42 43 44 45 46 47 48 49 50 ... 58 59

Keine Kommentare

Quickdata Quikstop-15 Spezifikationen Seite 45