topic Is there a need for for the status command when stopping a forwarder? in Getting Data In

Is there a need for for the status command when stopping a forwarder?

ddrillic — Wed, 08 Nov 2017 02:12:51 GMT

When stopping a forwarder I see the following -

bash-3.2$ ./splunk stop
splunkd is not running.
bash-3.2$ ./splunk status
splunkd 7085 was not running.
Stopping splunk helpers...

Done.
Stopped helpers.
Removing stale pid file... done.

bash-3.2$ ./splunk status
splunkd is not running.

So, do I really need to run the ./splunk statuswhen stopping a forwarder?

Re: Is there a need for for the status command when stopping a forwarder?

mayurr98 — Wed, 08 Nov 2017 11:29:48 GMT

If your job is just to stop the forwarder then you really do not need to write ./splunk status. Instead just type ./splunk stop

In other words, you do not really need to run the ./splunk status when stopping a forwarder

Re: Is there a need for for the status command when stopping a forwarder?

ddrillic — Sat, 11 Nov 2017 23:04:53 GMT

But you see, by running ./splunk status two things took place -

 Stopped helpers.
 Removing stale pid file... done.

One would think that these two actions actually belong to the invocation of ./splunk stop. Why are they done via ./splunk status?