[kepler-dev] [Bug 5321] New: sensor settings made by kepler user lost on SPAN restart
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Wed Feb 23 12:26:50 PST 2011
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5321
Summary: sensor settings made by kepler user lost on SPAN
restart
Product: Kepler
Version: 2.1.0
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: sensor-view
AssignedTo: barseghian at nceas.ucsb.edu
ReportedBy: barseghian at nceas.ucsb.edu
QAContact: kepler-dev at kepler-project.org
Estimated Hours: 0.0
To start SPAN you
generate a config file from a CRBasic program:
./cr_parser.py conf/sq110_and_bps.CR8 span.cfg
and then start SPAN using it:
./cr1k_d CR800 span.cfg
./dcd_mgr span.cfg
Currently SPAN crashes periodically, requiring restart. Even if that weren't
the case, we still need to function smoothly when the gumstix power cycles
(thus restarting SPAN). If a user makes sensor changes via Kepler, and then
SPAN is restarted, since the CRBasic program is never updated, the user sensor
settings are lost.
Possible solutions, neither of which are currently supported afaik, seem to be:
1) download from the logger the CRBasic program whenever changes are made, thus
keeping it in sync.
2) simply start SPAN without overwriting existing settings on the logger, e.g.
with a mostly blank config.
--
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the Kepler-dev
mailing list