Issuing a smithctl stop on an agent which has a lengthy cleanup process (say, flushing databases to disk) causes the agent to disappear from smithctl list -la almost immediately, while the agent is still up and running. This gives a false impression that work which requires the agent to be stopped can proceed, when in fact the agent is still performing its shutdown tasks.
Issuing a
smithctl stopon an agent which has a lengthy cleanup process (say, flushing databases to disk) causes the agent to disappear fromsmithctl list -laalmost immediately, while the agent is still up and running. This gives a false impression that work which requires the agent to be stopped can proceed, when in fact the agent is still performing its shutdown tasks.