Hard-coded data in /etc/init.d/vmchecker

[rhobincu]

The working directory, daemon executable path and user name are hard-coded in the /etc/init.d/vmchecker script. This information should be externally editable in a configuration file and/ or edit instructions should be present in the INSTALL file.

[cojocar]

Istallation of this file should be triggered when running pyton setup.py install. Another thing is the course name for which this file is installed. How many times do we have to start the queue daemon? Is it once per tester, once per course deployement?

[valenting]

It should be called for every course.
On Sep 20, 2014 6:55 PM, "cojocar" notifications@github.com wrote:

Istallation of this file should be triggered when running pyton setup.py
install. Another thing is the course name for which this file is
installed. How many times do we have to start the queue daemon? Is it once
per tester, once per course deployement?

—
Reply to this email directly or view it on GitHub
#64 (comment).

[cojocar]

So if you deployed multiple courses on the same machine (one unix
account for each course), what will be the name (path) of this script?

I propose to have a copy (called /etc/init.d/vmchecker) and then use
soft links (called /etc/init.d/vmchecker-${course_id}) to start the
queue for each ${course_id}.

On 09/20/2014 06:18 PM, Valentin Gosu wrote:

It should be called for every course.
On Sep 20, 2014 6:55 PM, "cojocar" notifications@github.com wrote:

Istallation of this file should be triggered when running pyton setup.py
install. Another thing is the course name for which this file is
installed. How many times do we have to start the queue daemon? Is it
once
per tester, once per course deployement?

—
Reply to this email directly or view it on GitHub
#64 (comment).

—
Reply to this email directly or view it on GitHub
#64 (comment).

[valenting]

It would be good if vmchecker-init-course created that link.

On 20 September 2014 19:33, cojocar notifications@github.com wrote:

So if you deployed multiple courses on the same machine (one unix
account for each course), what will be the name (path) of this script?

I propose to have a copy (called /etc/init.d/vmchecker) and then use
soft links (called /etc/init.d/vmchecker-${course_id}) to start the
queue for each ${course_id}.

On 09/20/2014 06:18 PM, Valentin Gosu wrote:

It should be called for every course.
On Sep 20, 2014 6:55 PM, "cojocar" notifications@github.com wrote:

Istallation of this file should be triggered when running pyton setup.py
install. Another thing is the course name for which this file is
installed. How many times do we have to start the queue daemon? Is it
once
per tester, once per course deployement?

—
Reply to this email directly or view it on GitHub
#64 (comment).

—
Reply to this email directly or view it on GitHub
#64 (comment).

—
Reply to this email directly or view it on GitHub
#64 (comment).