Authenticate against the CLUSTER_HOST via ssh rather than against the ChRIS database.
Run local and mosix jobs as the logged in unix user.

Problems to solve:

1) chmod -R 755 after a job completed so the chris user has guaranteed access
2) chmod 777 on the feed directory whenever the feed is shared so the slave (person who was shared with) has write access as well
Create a chris.run file which executes the command and the chmod -R 755 when the command is done.

This was required since mosbatch only accepts one program to run. An advantage is that a job can be easily run again using this (executable) file.

I do observe some slow performance in job scheduling which might be a temporary thing?

Also, we still need to fix the chmod 777 whenever a feed is shared.
Add preview for .run files.
Reduce the SSH logins for one job submission to 3.

This makes it much faster.

A chris.param file is not needed anymore since we have chris.run.

Also, I think it might be possible to combine it all to maximal 2 ssh logins when we create the job directoy not before launching the job.

This way it might be possible to detect whether a job was "queued" or is actually "running".
Change the permissions during sharing to 777 so that the slave user (the one who the feed got shared with) can write to the folder as well.
Merge branch 'master' into sshauthentication
Remove one ssh command when scheduling a job.
Merge branch 'master' into sshauthentication
Merge master.
Merge branch 'sshauthentication'