From e7cdd173a62a917a4b076bd660df86aae685e8ab Mon Sep 17 00:00:00 2001 From: Alex Dadgar Date: Fri, 4 Nov 2016 15:25:12 -0700 Subject: [PATCH] Fixes to stop command --- website/source/docs/commands/stop.html.md.erb | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/website/source/docs/commands/stop.html.md.erb b/website/source/docs/commands/stop.html.md.erb index 372993b7e..f43261012 100644 --- a/website/source/docs/commands/stop.html.md.erb +++ b/website/source/docs/commands/stop.html.md.erb @@ -22,10 +22,9 @@ cancel. If there is an exact match based on the provided job ID or prefix, then the job will be cancelled. Otherwise, a list of matching jobs and information will be displayed. -Upon successful deregistration, an interactive monitor session will start to -display log lines as the job unwinds its allocations and completes shutting -down. The monitor will exit once all allocations are stopped and the job has -reached a terminal state. It is safe to exit the monitor early using ctrl+c. +Stop will issue a request to deregister the matched job and then invoke an +interactive monitor that exits automatically once the scheduler has processed +the request. It is safe to exit the monitor early using ctrl+c. ## General Options @@ -38,10 +37,10 @@ reached a terminal state. It is safe to exit the monitor early using ctrl+c. which can be used to examine the evaluation using the [eval-status](/docs/commands/eval-status.html) command. -## Status Options - * `-verbose`: Show full information. +* `-yes`: Automatic yes to prompts. + ## Examples Stop the job with ID "job1":