)]}' { "log": [ { "commit": "d22c991c6a7a8126d567d5c4a29cdf55251f6dcc", "tree": "761ebd344fb443a22acdb71d1da6c5db6e889fa4", "parents": [ "287b4ae810ab3073e2c6e617f4e751758609dde9" ], "author": { "name": "Bob Lantz", "email": "lantz@onlab.us", "time": "Thu Dec 15 14:26:18 2016 -0800" }, "committer": { "name": "Jonathan Hart", "email": "jono@onlab.us", "time": "Thu Jan 19 23:38:10 2017 +0000" }, "message": "Improvements for init.d, upstart, and systemd-based systems\n\n1. Change ownership of /onos/apps\n\nonos-service needs write access to onos/apps/foo in order to activate\nan app. This also means that ONOS itself could also activate/deactivate,\nmodify, or reinstall apps, which seems a bit dodgy but is probably\nintended.\n\n2. Fix sudo command line\n\nThe -b option was in the wrong place, breaking sudo on systems where\nwe use sudo to start onos (e.g. older debian or centos.)\n\n3. Redirect stderr of \u0027type daemon\u0027 command\n\nWe want to detect whether the \u0027daemon\u0027 function/script is available\nin init.d enviroments that support it, and we do so using the type\ncommand. Previously we didn\u0027t redirect stderr, so this resulted\nin a confusing error message being sent to stderr of whoever is\ninvoking the script.\n\n4. onos.conf has changed to be more consistent with onos.initd\n\nPreviously onos.conf ignored $ONOS_GROUP and had a slightly different\nstructure.\n\n5. onos.service has been added for systemd-based systems\n\nThis initial version of onos.service calls /etc/init.d/onos to start\nand stop ONOS. In the future we may be able to call onos-service\ndirectly, but we will need to make sure that permissions are set up\ncorrectly so that onos-service can activate apps and so that ONOS\nitself can write its log files.\n\n6. A README has been added\n\n7. Update the onos-install and onos-uninstall scripts\n\nRelated Jira issue: ONOS-5550\n\nChange-Id: Ie72775f1d0a4082af9c5ea9b13999c427c15ffe0\n" } ] }