Hi Tobias

OK, done that. I should mention though that I'm not completely happy with the bug fix that I mentioned below. The problem is that the same login form is presented from three different places: login.php, team/index.php and jury/index.php. Self-registration works only from the first of those. My hack fix is to replicate the call to do_register that's within public/login.php within team/init.php but that leaves the anomalous situation that you also get offered a self-registration option if you navigate into jury/index. It doesn't work (and I doubt we want it to!) but I don't think it should even be presented as an option. I haven't fixed that.

We have one other local patch that may or may not interest you. [I haven't pushed it to the repository.]  On one of our servers we have a regular series of contests with old contests left running. We get lots of teams self-registering for just one contest, so soon get a scoreboard that's mostly full of non-participating teams. The patch is to limit the scoreboard display to just those teams that have made at least one submission to the contest that's being displayed.

Of course, for a major contest what you have is correct - you want to show all teams, including the ones that haven't submitted yet. To support both modes of operation you would need to have a configuration parameter to turn on and off display of all teams. However, I know that you're trying to limit the number of configuration parameters so you might not wish to go down this path.

The patch is of course simple: within the getTeams() function in lib/www/scoreboard.php, just add to the query the line

INNER JOIN submission USING (cid, teamid)

I did consider doing this with a filter or checkbox on the scoreboard but that didn't seem right. It's a fundamental difference in the scoreboard role: with lots of users, only some involved in this contest, it never makes sense to show them all.

Richard

On 08/05/16 18:16, Tobias Werth wrote:
Richard: that sounds like useful changes in general. Can you create a
pull request for these?

On 05/07/16 23:54, Richard Lobb wrote:
Hi Huynh Anh Dung

I don't think affiliations are included in the self-registration
capabilities of the current DOMjudge release. We patched our own local
version to do them. I attached our modified version of the file
domserver/lib/www/auth.php. It requires users to select from the
existing list of affiliations known to the site, or NOT KNOWN otherwise.
It comes with no guarantees, but it work for us.

There's also a bit of an issue with self-registration: it works only if
you get to the login screen by clicking the 'login' button, but not when
you get to the same page by other routes, e.g. you enter an url like
<servername>/team.index.php. A hack to fix that bug: in
domserver/www/team/index.php, add a line after line 29 so that lines 29
to 30 read:

if ( @$_POST['cmd']=='login' ) do_login();
if ( @$_POST['cmd']=='register' ) do_register();  // ** ADD THIS LINE **

Hope that helps

Richard

On 08/05/16 08:58, Huynh Anh Dung wrote:
Hi Jaap,
Please help how can enable affiliations in self register section.
Thanks Jaap
Nice week end.
Best regards

Lec. Huỳnh Anh Dũng
FPT UNIVERSITY.
http://www.fpt.edu.vn

-----Original Message-----
From: DOMjudge-devel [mailto:domjudge-devel-bounces@domjudge.org] On
Behalf Of Jaap Eldering
Sent: Saturday, April 30, 2016 8:29 PM
To: domjudge-devel@domjudge.org
Subject: Re: Please help

On 30-04-16 01:24, Huynh Anh Dung wrote:
When I run ./configure
checking for cgroup_init in -lcgroup... yes

  * default user........: root
  * runguard user.......: domjudge-run
  * webserver group.....: www-data
     - chroot...........: /chroot/domjudge
     - cgroup...........: /cgroup
Up to this stage, I don’t know it is or not enable
What I'm looking for is actually the line below "webserver group" that
says:

  * use Linux cgroups...: yes/no

But when I logged in to your machine, /root/domjudge-5.1.1/config.log
shows that cgroups are disabled. You have the package installed, but
have not edited /etc/default/grub, so the kernel doesn't support
cgroups yet.

As a side note, you should not install DOMjudge as root user. Instead
create a separate user to install it as: DOMjudge will use 'sudo' to
obtain root privileges only when needed.

Jaap


Did you install or copy runguard to the judgehost installation
(under judgehost/bin)? This step is not explicitly listed in the
documentation.
Not yet it is not listed in the document Best

Lec. Huỳnh Anh Dũng
ACM/ICPC SUPERVISOR
FPT UNIVERSITY.
http://www.fpt.edu.vn

-----Original Message-----
From: DOMjudge-devel [mailto:domjudge-devel-bounces@domjudge.org] On
Behalf Of Jaap Eldering
Sent: Saturday, April 30, 2016 10:57 AM
To: domjudge-devel@domjudge.org
Subject: Re: Please help

On 30-04-16 00:51, Huynh Anh Dung wrote:
Hi,
I do follow exact with the help file and I do up to:
-Install the necessary packages: # apt-get install libcgroup-dev (or
# yum install libcgroup-devel on RedHat)
- Edit grub config to add memory cgroup and swap accounting to the
boot options. Edit /etc/default/grub and change the default
commandline to GRUB_CMDLINE_LINUX_DEFAULT="quiet
cgroup_enable=memory swapaccount=1". Then run update-grub and reboot.
-Compile DOMjudge with cgroup support. Re-run ./configure and look
for cgroup in the output.
And did the configure output say that cgroups were enabled?

How to rebuild : Then rebuild the runguard with make build. I only
make all after re-run ./configure
Did you install or copy runguard to the judgehost installation (under
judgehost/bin)? This step is not explicitly listed in the documentation.

Jaap


Upto that point, then I run ./judgedaemon Then I said no cgroup Best

Lec. Huỳnh Anh Dũng
ACM/ICPC SUPERVISOR
FPT UNIVERSITY.
http://www.fpt.edu.vn

-----Original Message-----
From: Jaap Eldering [mailto:jaap@jaapeldering.nl]
Sent: Saturday, April 30, 2016 10:45 AM
To: Huynh Anh Dung <dungha@fpt.edu.vn>; domjudge-devel@domjudge.org
Subject: Re: Please help

On 30-04-16 00:28, Huynh Anh Dung wrote:
Hi,
I do install Cgroup follow but when I run ./judgedaemon it said
"Not using cgroup"
help
When you (re)ran configure did it say that cgroups were enabled?

Did you recompile and reinstall runguard (or the whole judgehost
installation)?

Jaap


-----Original Message-----
From: Jaap Eldering [mailto:jaap@jaapeldering.nl]
Sent: Saturday, April 30, 2016 7:37 AM
To: Huynh Anh Dung <dungha@fpt.edu.vn>
Subject: Re: Please help

On 29-04-16 21:26, Huynh Anh Dung wrote:
Hi Jaap,
Can you look at 2 lines :
# exec java -client -Xss8m -Xmx${MEMLIMITJAVA}k -DONLINE_JUDGE=1
-DDOMJUDGE=1 '$MAINCLASS'
exec java -client  -Xmx3g -DONLINE_JUDGE=1 -DDOMJUDGE=1 '$MAINCLASS'
before you change and  successfully run, I already change.
I recommend not to change it like that: then if you change the
configured global memory limit, it will not affect Java submissions.
Also, if you now reduce the memory limit below 3 GB, then java
submissions will automatically crash because the JVM is trying to
allocate more memory than is allowed by DOMjudge. NOTE: DOMjudge
imposes the memory limit onto the whole Java VM, that's why this
this whole MEMRESERVED variable is needed in the first place.

Jaap

P.S. If you have further questions, please return to using the
mailinglist.


            
_______________________________________________
DOMjudge-devel mailing list
DOMjudge-devel@domjudge.org
https://www.domjudge.org/mailman/listinfo/domjudge-devel

_______________________________________________
DOMjudge-devel mailing list
DOMjudge-devel@domjudge.org
https://www.domjudge.org/mailman/listinfo/domjudge-devel

_______________________________________________
DOMjudge-devel mailing list
DOMjudge-devel@domjudge.org
https://www.domjudge.org/mailman/listinfo/domjudge-devel


_______________________________________________
DOMjudge-devel mailing list
DOMjudge-devel@domjudge.org
https://www.domjudge.org/mailman/listinfo/domjudge-devel


      

_______________________________________________
DOMjudge-devel mailing list
DOMjudge-devel@domjudge.org
https://www.domjudge.org/mailman/listinfo/domjudge-devel