The above commands work well when you have not logged out of the cluster while running the job. Because of the cluster's setup, there are many nodes that could be running your job. When you log in to the cluster, you are automatically sent to a particular node econ7 through econ18. This might not be the same node that is running your job. To get to a particular nod use

ssh econ7

And then to see processes that are running under your username in this node:

ps ux

If your job is computationally demanding, you might want to check if the node is not busy before running it. See the next subsection on how to list current jobs.

Once you have a job running, you might want to change it's priority or stop it. To check on the list of running jobs, use the command

htop

You can also see all running jobs statically with

ps -aef

This prints a very large number of jobs, so you might prefer to filter the output. You can do this with the command grep:

ps -aef | grep <your username>

Each line represents a single process. The leftmost column is the process id, and the second leftmost column is the user that owns a process. You can filter the list of processes by username. Type 'u' and then your username and then enter. All of your processes should show up.

To stop a process, note the process id number on the left hand side when using top. Type 'k', and then the process id, and then press enter.

Alternatively, press 'q' to stop top. Then, type use the

kill

command.

kill <process id>

You can change how many CPU cycles are given to your job by using the command

renice

. Once you know the process id, you can use the command:

renice -n <priority> -p <process id>

to change the niceness of your process. If you are running a computationally intensive job, please set your job to a high niceness level, so that you don't monopolize cluster resources :)