Contents

Feature: killall
  @sudo
  Scenario: killall controller_name
    Given I set the environment variables to:
      | variable         | value |
      | TREMA_LOG_DIR    | .     |
      | TREMA_PID_DIR    | .     |
      | TREMA_SOCKET_DIR | .     |
    And a file named "null_controller.rb" with:
      """ruby
      class NullController < Trema::Controller; end
      """
    And a file named "trema.conf" with:
      """ruby
      vswitch { datapath_id 0xabc }
      vhost('host1') { ip '192.168.0.1' }
      vhost('host2') { ip '192.168.0.2' }
      link '0xabc', 'host1'
      link '0xabc', 'host2'
      """
    And a file named "void_controller.rb" with:
      """ruby
      class VoidController < Trema::Controller; end
      """
    And I successfully run `trema run null_controller.rb -c trema.conf -d`
    And I successfully run `trema run void_controller.rb -p 6654 -d`
    When I successfully run `trema killall NullController`
    Then virtual links should not exist 
    And the following files should not exist:
      | NullController.pid |
      | vhost.host1.pid    |
      | vhost.host2.pid    |
    And the following files should exist:
      | VoidController.pid |

  @sudo
  Scenario: "Controller process does not exist" error
    When I run `trema killall NO_SUCH_NAME`
    Then the exit status should not be 0
    And the output should contain:
    """
    Controller process "NO_SUCH_NAME" does not exist.
    """

Version data entries

3 entries across 3 versions & 1 rubygems

Version	Path
trema-0.10.1	features/trema_killall/killall.feature
trema-0.10.0	features/trema_killall/killall.feature
trema-0.9.0	features/trema_killall/killall.feature