Commit Graph

5 Commits (3a22eea5bab20414e809860141868b99cad0d6e4)

Author SHA1 Message Date
Matthew D. Scholefield 10bd9a1cf3 Change initial kill to SIGINT
This sends a ctrl+c signal to each process which will allow code to exit properly by handling KeyboardInterrupt
Other notable changes:
 - create_daemon method used to clean up create daemon threads
 - create_echo_function used to reduce code duplication with messagebus
 echo functions
 - wait_for_exit_signal used to wait for ctrl+c (SIGINT)
 - reset_sigint_handler used to ensure SIGINT will raise KeyboardInterrupt
2018-04-11 21:29:10 -05:00
Åke Forslund d6c5c5c30e Add "all" option to stop-mycroft.sh
Adding the "all" option makes the syntax for stop-mycroft.sh mirror the syntax
for start-mycroft.sh
2017-11-09 10:41:24 -06:00
Rhett Aultman 35c3af1e2c Make mycroft-core.sh invocable from outside
mycroft-core.sh has a relative-path call (that itself also likes to
be called from inside mycroft-core) that prevents making a clean start
of mycroft from outside the mycroft-core directory.  This makes doing
things like adding it as a Ubuntu Unity startup application slightly
messy.
2017-10-26 19:06:11 -04:00
Steve Penrod 37a798385e Remove unused variable noticed by Codacy
Removed the unused exit_code variable
2017-09-28 01:08:20 -05:00
Steve Penrod 07992b49d5 Revamping the scripts used to start/stop Mycroft
Reworking the mechanisms used to interact with Mycroft.  The old
mycroft.sh utilized the 'screen' command, but now with the CLI it
it easier to use that for viewing log files.  Plus there was
confusion between when to use start.sh and when to use mycroft.sh.

Now things are wrapped in the simple and easily discoverable scripts:
* start-mycroft.sh
* stop-mycroft.sh

The start-mycroft.sh allows you to start the background services and
to invoke the various tools (e.g. the CLI, unit tests, etc).

==== Fixed Issues ====

====  Documentation Notes ====
This will require revamp of the getting started guides, etc.
2017-09-28 01:08:20 -05:00