Work on user based control
authorSam Moore <[email protected]>
Mon, 14 Oct 2013 14:32:02 +0000 (22:32 +0800)
committerSam Moore <[email protected]>
Mon, 14 Oct 2013 14:32:02 +0000 (22:32 +0800)
commite3e7914fe2f59765e5f92371329652a02518928c
tree4f55aa76b3009387c4ecbb037d5a40f5ed789d96
parent450583abb79d5fedb0debabed073d9b191dac80c
Work on user based control

Test file shadow (password matches username *cough*) for login purposes.

When a user gains FCGI_LockControl, a directory is created (if it doesn't exist).
Control_Handler will operate from the directory of the currently logged in user.

The user who owns the currently running experiment must match a user who wants to control it.
Alternately an administrator can pass "force"

Consider generalising this to also apply to actuators (since any user can change the actuator control :S).

Also it's horribly messy and terrible and all in the Control_Handler at the moment.

FCGI_Context should probably store a lot of the information that the g_controls structure is storing at the moment? Merge/replace?
server/actuator.c
server/actuators/filetest.c
server/control.c
server/fastcgi.c
server/fastcgi.h
server/login.c
server/main.c
server/options.h
server/parameters
server/sensor.c
server/shadow [new file with mode: 0644]

UCC git Repository :: git.ucc.asn.au