X-Git-Url: http://mj.ucw.cz/gitweb/?a=blobdiff_plain;f=config;h=950d03e1ed3f22311cd639dcc4380b82afb26f61;hb=3ee84a61340017dccf73f53194cd7ec4c7ec838b;hp=84bf889b68dce056625b86d0eef75c4d1c78bc61;hpb=d8ffb1d8f28c456bee59730816a5ee276da76399;p=eval.git

diff --git a/config b/config
index 84bf889..950d03e 100644
--- a/config
+++ b/config
@@ -1,41 +1,121 @@
-# Configuration file for MO Evaluator
-# (c) 2001 Martin Mares <mj@ucw.cz>
+# Configuration file for the MO Evaluator
+# (c) 2001--2004 Martin Mares <mj@ucw.cz>
 
-# Directories and users
-MO_ROOT=/home/mo
+# The root of the whole directory hierarchy
+MO_ROOT=/aux/mo
+
+# User and group used by the evaluator itself
 EVAL_USER=mo-eval
 EVAL_GROUP=mo-eval
-TEST_USERS="mo-test1 mo-test2"
 
-# UID range assigned to contestants
-CT_UID_MIN=21000
-CT_UID_MAX=29999
+# Test user for the sandbox. You can let mo-setup create more test users
+# and then run several evaluators in parallel, each in its own sandbox.
+# For testing, you can also leave TEST_USER undefined and run the sandbox
+# with EVAL_USER privileges, but beware, this is INSECURE.
+#TEST_USER=${TEST_USER:-mo-test1}
+TEST_USERS="mo-test1 mo-test2"
 
-# Test user for sandboxing
-TEST_USER=${TEST_USER:mo-test1}
+# Sometimes we need to get a list of all contestants (not in the evaluator
+# itself, but in various auxiliary scripts). In such cases we call mo-get-users,
+# which either scans /etc/passwd for users with UID in the following range,
+# or uses an explicit list of contestants CT_USER_LIST (username<tab>fullname).
+#CT_UID_MIN=65100
+#CT_UID_MAX=65199
+CT_USER_LIST=userlist
 
-### all of the following variables can be overriden in per-task config file
+### Per-task configuration variables (default values, override in per-task config)
 
-# Default task type (file or interactive)
-TASK_TYPE=file
+## Compiler settings:
 
 # Known source file extensions
 EXTENSIONS="c C cpp p pas"
 
-# Extra compiler flags (null, but can be overriden)
+# Extra compiler flags for C (null, but can be overriden)
 EXTRA_CFLAGS=
 
+# Extra compiler flags for Pascal
+EXTRA_PFLAGS=
+
 # For each source extension, we must give compiler command
 COMP_c='/usr/bin/gcc -O2 -g -o $EXE $EXTRA_CFLAGS $SRC'
 COMP_C='/usr/bin/g++ -O2 -g -o $EXE $EXTRA_CFLAGS $SRC'
 COMP_cpp="$COMP_C"
-COMP_p='/usr/bin/fpc -Ci -Cr -g -O2 -So -Sg -o$EXE $EXTRA_CFLAGS $SRC'
+COMP_p='/usr/bin/fpc -Ci -Cr -g -O2 -So -Sg -o$EXE $EXTRA_PFLAGS $SRC'
 COMP_pas="$COMP_p"
 
 # Sandbox options used when compiling
-COMP_SANDBOX_OPTS='-m65536 -t60 -w -e'
+COMP_SANDBOX_OPTS='-m65536 -t60 -w -e -i/dev/null'
+
+# Sandbox initializaton commands for compilation
+COMP_SANDBOX_INIT=
+
+# List of extra files needed for compilation. They are copied to the compiler
+# sandbox from the problem's directory.
+#COMP_EXTRAS="extras.h"
+
+## Tester settings (most can be overriden in per-test config):
+
+# The following variables are automatically set by the evaluator:
+# PROBLEM	name of the problem
+# HDIR		home directory of the evaluator (i.e., this file is $HDIR/config)
+# PDIR		directory containing problem data
+# SDIR		directory containing contestant's solution
+# TDIR		directory containing testing results
+# TMPDIR	directory containing temporary files
+# TEST		name of the current test
+
+# Task type:
+# offline	off-line task
+# interactive	interactive task communicating via stdio with a testing program
+# open-data	open-data task (i.e., we don't submit program, but output files)
+TASK_TYPE=file
+
+# I/O type (IO_TYPE sets defaults for IN_TYPE and OUT_TYPE)
+# file		input from $PROBLEM.in, output to $PROBLEM.out (possible even for interactive tasks)
+# stdio		input from stdin, output to stdout
+# none		no input/output
+IO_TYPE=stdio
+#IN_TYPE=stdio
+#OUT_TYPE=stdio
+
+# A list of all tests
+TESTS="1 2 3 4 5 6 7 8 9 10"
+
+# A list of public tests (executed by submit and check scripts)
+SAMPLE_TESTS="0"
+
+# Number of points per test
+POINTS_PER_TEST=1
+
+# Time limit in seconds
+TIME_LIMIT=10
+
+# Memory limit in kilobytes
+MEM_LIMIT=16384
+
+# Command used to check output syntax (optional)
+# Returns exit code 1 if syntax is wrong, 0 if correct
+# fd1 is connect to evaluator log, feel free to log anything
+# fd2 is an optional one-line verdict
+#SYNTAX_CHECK='grep -v -- - $TDIR/$TEST.out'
+
+# Command used to check output correctness
+# Returns exit code 1 if output is incorrect, 0 if correct
+# fd1 is connect to evaluator log, feel free to log anything
+# fd2 is an optional one-line verdict
+# The checker can generate $TDIR/$TEST.pts to assign points irregularly
+OUTPUT_CHECK='diff -bBu $TDIR/$TEST.ok $TDIR/$TEST.out'
+
+# Checker for interactive tasks
+# Returns exit code 1 if test failed, 0 if passed
+# fd1 is connect to evaluator log, feel free to log anything
+# fd2 is an optional one-line verdict
+# The checker can generate $TDIR/$TEST.pts to assign points irregularly
+#IC_CHECK='$PDIR/checker $PDIR/$TEST.in $PDIR/$TEST.chk'
 
 # Sandbox options used when testing
 TEST_SANDBOX_OPTS='-a2 -f -m$MEM_LIMIT -t$TIME_LIMIT'
 # -w for wall clock measuring
-# For stdio tasks append '-i$PROBLEM.in -o$PROBLEM.out'
+
+# Sandbox initialization commands
+SANDBOX_INIT=