Ticket #724 (closed defect: fixed)

Opened 10 years ago

Last modified 10 years ago

user allowed to run start_seattle.sh before install.sh without complaint

Reported by: jsamuel Owned by: zackrb
Priority: major Milestone:
Component: installer Version: 0.1o
Severity: Medium Keywords:
Cc: Blocking:
Blocked By:


It's possible to run start_seattle.sh without running install.sh. There's no feedback to the user (e.g. "you must run the installer first") and it results in the nodemanager and softwareupdater processes running. The nodemanager won't do much good at that point.

Change History

Changed 10 years ago by jsamuel

  • milestone 0.1o deleted

Changed 10 years ago by zackrb

Possible solution: Add a key in the nodeman.cfg file that states whether or not seattle has been installed. Would the uninstaller want to reset this value, even though the Node Manager keys will have already been generated? Probably just for consistency's sake (plus who knows what will be added in the future that will need the installer to be run again if the uninstaller has been installed).

Changed 10 years ago by zackrb

  • status changed from new to closed
  • resolution set to fixed

A new boolean value has been added to nodeman.cfg ('seattle_installed'). The installer and uninstaller set this value accordingly. The start_seattle scripts for all platforms check this value and either start seattle or produce an error message stating the seattle must first be installed before it can be started. See r3325

Note: See TracTickets for help on using tickets.