From bd8a36cc58f5c3193c887296752b7cacf53655a5 Mon Sep 17 00:00:00 2001 From: Alex Dadgar Date: Tue, 31 Oct 2017 16:49:12 -0700 Subject: [PATCH] use job status --- .../docs/operating-a-job/inspecting-state.html.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/website/source/docs/operating-a-job/inspecting-state.html.md b/website/source/docs/operating-a-job/inspecting-state.html.md index 5d7aa7800..10908b545 100644 --- a/website/source/docs/operating-a-job/inspecting-state.html.md +++ b/website/source/docs/operating-a-job/inspecting-state.html.md @@ -22,11 +22,11 @@ and command largely apply to all jobs in Nomad. ## Job Status -After a job is submitted, you can query the status of that job using the status -command: +After a job is submitted, you can query the status of that job using the job +status command: ```shell -$ nomad status +$ nomad job status ``` Here is some sample output: @@ -37,11 +37,11 @@ docs service 50 running ``` At a high level, we can see that our job is currently running, but what does -"running" actually mean. By supplying the name of a job to the status command, -we can ask Nomad for more detailed job information: +"running" actually mean. By supplying the name of a job to the job status +command, we can ask Nomad for more detailed job information: ```shell -$ nomad status docs +$ nomad job status docs ``` Here is some sample output @@ -81,7 +81,7 @@ If we issue the status command with the `-evals` flag, we could see there is an outstanding evaluation for this hypothetical job: ```text -$ nomad status -evals docs +$ nomad job status -evals docs ID = docs Name = docs Type = service