1. 08 Mar, 2016 4 commits
    • Change-Id: Ib4f043af142c40835882bdbbc60ced61836abde8
      Thomas Vachuska authored
    • Change-Id: I3299d991a7d53544cb81d74d31164140d7d36d06
      Simon Hunt authored
    • 1.  Invoke karaf script in all cases (upstart, initd/systemd)
      
      This means that onos-service now blocks, which means we need to
      change onos.initd to run it in the background. Otherwise, we could
      use karaf/bin/start
      
      This should fix ONOS-4117
      
      2. Use service onos {start/status/etc.} for upstart/init/systemd
      
      onos-install should not invoke the new init.d script directly;
      instead it should use service onos {cmd, which should work if
      service is available on upstart, init.d, and systemd-based
      distributions.
      
      This should fix ONOS-4124
      
      3. In onos.initd, check if ONOS is running.
      
      This makes it easier to see what is going on, and it also avoids
      attempting to start ONOS if it's already running.
      
      Change-Id: I0152fd7fdcb079b25531442315d0bd69e6c7653d
      Bob Lantz authored
    • Change-Id: I5873d1476ac68e6c2ee4462e629b00313214ef36
      Simon Hunt authored
  2. 07 Mar, 2016 12 commits
  3. 05 Mar, 2016 6 commits
  4. 04 Mar, 2016 18 commits