1 # Configuration file for the MO Evaluator
2 # (c) 2001--2007 Martin Mares <mj@ucw.cz>
4 # The root of the whole directory hierarchy
5 if [ -z "$MO_ROOT" ] ; then
9 # User and group used by the evaluator itself
13 # Test user for the sandbox. You can let mo-setup create more test users
14 # and then run several evaluators in parallel, each in its own sandbox.
15 # For testing, you can also leave TEST_USER undefined and run the sandbox
16 # with EVAL_USER privileges, but beware, this is INSECURE.
17 #TEST_USER=${TEST_USER:-mo-test1}
18 TEST_USERS="mo-test1 mo-test2"
20 # These values are used when creating logins for eval and contestanst.
25 # Sometimes we need to get a list of all contestants (not in the evaluator
26 # itself, but in various auxiliary scripts). In such cases we call mo-get-users,
27 # which either uses an explicit list of contestants CT_USER_LIST (username<tab>fullname),
28 # or (if undefined) scans /etc/passwd for users with UID between CT_UID_MIN and CT_UID_MAX.
31 ### Per-task configuration variables (default values, override in per-task config)
35 # Known source file extensions
36 EXTENSIONS="c cc C cpp p pas"
38 # Extra compiler flags for C (null, but can be overriden)
41 # Extra compiler flags for Pascal
44 # For each source extension, we must give compiler command
45 COMP_c='/usr/bin/gcc -std=gnu99 -O2 -g -o $EXE $EXTRA_CFLAGS $SRC'
46 COMP_C='/usr/bin/g++ -O2 -g -o $EXE $EXTRA_CFLAGS $SRC'
49 COMP_p='/usr/bin/fpc -Ci -Cr -Ct -g -O2 -Sg -o$EXE $EXTRA_PFLAGS $SRC'
52 # Sandbox options used when compiling
53 COMP_SANDBOX_OPTS='-m65536 -t60 -w -e -i/dev/null'
55 # Sandbox initialization commands for compilation
58 # List of extra files needed for compilation. They are copied to the compiler
59 # sandbox from the problem's directory.
60 #COMP_EXTRAS="extras.h"
62 ## Tester settings (most can be overriden in per-test config):
64 # The following variables are automatically set by the evaluator:
65 # PROBLEM name of the problem
66 # HDIR home directory of the evaluator (i.e., this file is $HDIR/config)
67 # PDIR directory containing problem data
68 # SDIR directory containing contestant's solution
69 # TDIR directory containing testing results
70 # TMPDIR directory containing temporary files
71 # TEST name of the current test
74 # offline off-line task
75 # interactive interactive task communicating via stdio with a testing program
76 # open-data open-data task (i.e., we don't submit program, but output files)
79 # I/O type (IO_TYPE sets defaults for IN_TYPE and OUT_TYPE)
80 # file input from $PROBLEM.in, output to $PROBLEM.out (possible even for interactive tasks)
81 # stdio input from stdin, output to stdout
82 # none no input/output
88 TESTS="1 2 3 4 5 6 7 8 9 10"
90 # A list of public tests (executed by submit and check scripts)
93 # Number of points per test
96 # Time limit in seconds
99 # Memory limit in kilobytes
102 # Command used to check output syntax (optional)
103 # Returns exit code 1 if syntax is wrong, 0 if correct
104 # fd1 is connect to evaluator log, feel free to log anything
105 # fd2 is an optional one-line verdict
106 #SYNTAX_CHECK='grep -v -- - $TDIR/$TEST.out'
108 # Command used to check output correctness
109 # Returns exit code 1 if output is incorrect, 0 if correct
110 # fd1 is connect to evaluator log, feel free to log anything
111 # fd2 is an optional one-line verdict
112 # The checker can generate $TDIR/$TEST.pts to assign points irregularly
113 OUTPUT_CHECK='diff -bBu $TDIR/$TEST.ok $TDIR/$TEST.out'
115 # Checker for interactive tasks
116 # Returns exit code 1 if test failed, 0 if passed
117 # fd1 is connect to evaluator log, feel free to log anything
118 # fd2 is an optional one-line verdict
119 # The checker can generate $TDIR/$TEST.pts to assign points irregularly
120 #IC_CHECK='$PDIR/checker $PDIR/$TEST.in $PDIR/$TEST.chk'
122 # Sandbox options used when testing
123 TEST_SANDBOX_OPTS='-a2 -f -m$MEM_LIMIT -t$TIME_LIMIT'
124 # -w for wall clock measuring
126 # Sandbox initialization commands