The Installation of MO-Eval

MO-Eval can be installed in two possible ways:

Minimal Installation

Just invoke make and edit the top-level config file to suit your needs, leaving TEST_USER commented out.

In this setup, everything lives in the source tree you have started with and you don't need any special privileges for neither installation or running of the evaluator.

Beware: The evaluated programs are NOT fully separated from the evaluation environment and they could interfere with it. Use it only for playing with the package, not for any real competition.

Normal Installation

The recommended way is to let the evaluator use two user accounts. One (let's call the user mo-eval) runs the evaluator and keeps all secret files like the test data, another one (mo-test) runs the tested programs. There can be multiple test users if you want to run several evaluators in parallel. However, in practice the evaluation is so fast that this is seldom needed.

How to set up this installation:

Run make to compile all programs.
Edit config to suit your needs, in particular set MO_ROOT, EVAL_USER, EVAL_GROUP, TEST_USER and TEST_USERS.
Create $MO_ROOT (here we will assume that it's set to /aux/mo

Create the evaluation users:

	mo-eval:x:65000:65000:MO Evaluator:/aux/mo/eval/mo-eval:/bin/bash
	mo-test1:x:65001:65000:MO Tester 1:/aux/mo/eval/mo-test1:/bin/bash
	mo-test2:x:65002:65000:MO Tester 2:/aux/mo/eval/mo-test2:/bin/bash

And the evaluation group:
```
	mo-eval:x:65000:
```
Run bin/mo-install as root to create the directory hierarchy under $MO_ROOT install all parts of the evaluator there and set the correct access rights.
Log in as mo-eval and do everything else from there.
Later, you can reinstall parts of the hierarchy, without affecting the rest, by running:
- mo-create-public to update the public data available to contestants according to the contents of the public directory
- mo-create-testusers to update the home directory of the mo-test users.

Contestants' homes

MO-Eval can either take care of the home directories of contestants or use an existing infrastructure. In the former case, you need to do the following:

Set CT_UID_MIN and CT_UID_MAX in the top-level config file. (The evaluator users described above should be outside this range!).

Create the contestant users inside the UID range you defined; choose names as you wish:

	mo00:x:65100:65100:MO Contestant 00:/aux/mo/users/mo00/mo00:/bin/bash
	...
	mo99:x:65199:65199:MO Contestant 99:/aux/mo/users/mo99/mo99:/bin/bash

Create a group for each of these users (preferably with the same ID's):
```
	mo00:x:65100:
	...
	mo99:x:65199:
```
(You can use the bin/mo-create-logins script to automate this process, including printing of leaflets with passwords, but you will probably need to customize the script.)
Run bin/mo-create-contestants as root to create the home directories. (The permissions are set up so that the contestants cannot see each other's directory even if they want. However you still need to make sure that there is no directory all of them can write to, like the system-wide /tmp. In our contest, the users work on their own machines and only the home directories are shared across the network, so this problem doesn't arise.)
If multiple contestants work on the same machine remotely, you need to set quotas and other limits for them. On some systems, you cannot use limits.conf for that, because sshd applies the limits as root, so you either limit root or the limits don't work at all. In such cases, modify /etc/profile:
```
	if [ $UID -ge 65100 -a $UID -le 65199 ] ; then
		ulimit -Sc 8192		# core file size
		ulimit -SHu 32		# processes
		ulimit -SHn 256		# max open files
		ulimit -SHv 262144	# max virtual memory
	fi
```