Once you have compiled your program or have binaries installed correctly, you
should be able to execute them. This page provides some basic information on
how to run your jobs on Compute
Server or Lehigh Application Farm.
Suppose your binary is called foobin and is located in directory
/some/dir/ectory. To simply execute
foobin do:
/some/dir/ectory/foobin
To be able to run foobin the file foobin should have execute permission on it. If you dont have permission to execute foobin you will see an error:
bash: /some/dir/ectory/foobin: Permission denied
You can add permission to execute the file by doing:
chmod u+x /some/dir/ectory/foobin
Many times, the executable will throw out a lot of information. Suppose you wish to store this in a file foo.out. The output can be redirected by doing this:
/some/dir/ectory/foobin > foo.out
This will direct all output from foobin into foo.out. Using >> instead of > will append output to foo.out rather than overwriting it.
All error messages will however still be thrown to the stderr (the console). To direct error messages use the following:
/some/dir/ectory/foobin 1> foo.out 2> foo.err
This will redirect output to foo.out and error messages to foo.err. To redirect both output and error messages to same file:
/some/dir/ectory/foobin &> foo.out
or
/some/dir/ectory/foobin >foo.out 2>&1
To look at what all processes you are running on the machine you just logged into, to:
top -u user-name
It will bring up a table-of-processes. You can hit ? to see help on doing other things in top. Like killing, renice-ing, sorting etc. You can also list all your processes by doing:
ps aux|grep user-name
or
ps -ef|grep user-name