| Bob Lantz | d22c991 | 2016-12-15 14:26:18 -0800 | [diff] [blame] | 1 | ONOS "service" configuration files |
| 2 | |
| 3 | In order to run ONOS as a "service," whose execution is managed |
| 4 | by the OS, you can install an appropriate configuration/startup file. |
| 5 | |
| 6 | onos.initd: startup file for SysV/init.d-based systems |
| 7 | usually installed as /etc/init.d/onos |
| 8 | |
| 9 | onos.conf: configuration for upstart-based systems |
| 10 | usually installed as /etc/init/onos.conf |
| 11 | |
| 12 | onos.service: configuration for systemd-based systems |
| 13 | currently calls /etc/init.d/onos start |
| 14 | usually installed as /etc/systemd/system/onos.service |
| 15 | |
| 16 | The reason why onos.service currently calls /etc/init.d/onos |
| 17 | is because the init.d script fixes permissions that are required |
| 18 | by onos-service (such as /opt/onos/apps.) |