Hi,

You can add comments rather than answers.

Ok, I see your command-line. What was the output of that command-line?

António

Please use the ADD COMMENT box for discussion, the answer field is reserved for answers/solutions.

I think it shouldn't be killed because if you get an error it should print something like, even if gets killed:

Command exited with non-zero status 127
Command being timed: "lsn"
User time (seconds): 0.00
System time (seconds): 0.00
Percent of CPU this job got: ?%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.00
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 1160
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 0
Minor (reclaiming a frame) page faults: 27
Voluntary context switches: 1
Involuntary context switches: 0
Swaps: 0
File system inputs: 0
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 127

Although, I'm not 100% sure. Anyway I believe that @genomax answer (below) answers your question.

António