Commit f48f9f6e authored by Per Cederqvist's avatar Per Cederqvist
Browse files

Use the -f argument of lyskomd, not -d. Pass the reason argument to

lyskomd_death.
parent f932e8d1
......@@ -83,7 +83,7 @@ expect {
unset test
# Attempt to start a second lyskomd.
spawn ../lyskomd -d config/lyskomd-config
spawn ../lyskomd -f config/lyskomd-config
set test "lyskomd finds a lock"
expect {
-re "^Where does the trace want to go today. .stderr.$nl" {
......@@ -112,7 +112,7 @@ unset test
# Shut down lyskomd.
system "kill -HUP $lyskomd_pid"
lyskomd_death
lyskomd_death "" signal
# Start a new lyskomd.
lyskomd_start
......@@ -125,7 +125,7 @@ expect {
}
# Start a new lyskomd. Check that it removes the stale lock file.
set new_pid [spawn ../lyskomd -d config/lyskomd-config]
set new_pid [spawn ../lyskomd -f config/lyskomd-config]
set test "stale lock file removed"
expect {
-re "^Where does the trace want to go today. .stderr.$nl" {
......@@ -163,7 +163,7 @@ if {$bypass == 0} {
# Start a new lyskomd while a lock file for a remote system exists.
system "ln -s inet.lysator.liu.se:4711 db/lyskomd-lock"
spawn ../lyskomd -d config/lyskomd-config
spawn ../lyskomd -f config/lyskomd-config
set test "remote lock file found"
expect {
-re "^Where does the trace want to go today. .stderr.$nl" {
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment