# Standalone deployment & the mender-client daemon

**URL:** <https://hub.mender.io/t/standalone-deployment-the-mender-client-daemon/3986>\
**Category:** General Discussions\
**Created:** [August 9, 2021, 10:25pm UTC](https://hub.mender.io/t/standalone-deployment-the-mender-client-daemon/3986 "2021-08-09T22:25:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lmrogp](https://avatars.discourse-cdn.com/v4/letter/l/c4cdca/32.png) [@lmrogp](https://hub.mender.io/u/lmrogp)\
**Post date:** [August 9, 2021, 10:25pm UTC](https://hub.mender.io/t/standalone-deployment-the-mender-client-daemon/3986/1 "2021-08-09T22:25:50Z")

</div>

Hi all,

First-time poster and glad to be part of the community. I’m looking for some insight on how the daemon is disabled for standalone deployment.

The [Standalone Deployment](https://docs.mender.io/artifact-creation/standalone-deployment) page describes stopping Mender client running as a daemon in order to use standalone mode. The command given is **sudo systemctl stop mender-client**. I ran the command before doing a standalone update, and after a reboot, I was surprised to see the **mender-client.service** still listed as inactive. I would expect that state if I had done a **disable** , as opposed to a **stop**. Is the **mender -install** disabling the mender-client daemon as part of installation?

I don’t want the daemon to be active, but am curious about how it became disabled. I’m running Mender 2.6 with Debian Buster on a Raspberry Pi 3.

Thanks

---

<div class="post-metadata">

**Author:** ![oleorhagen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/oleorhagen/32/297_2.png) [@oleorhagen](https://hub.mender.io/u/oleorhagen)\
**Post date:** [August 10, 2021, 7:20am UTC](https://hub.mender.io/t/standalone-deployment-the-mender-client-daemon/3986/2 "2021-08-10T07:20:05Z")

</div>

Are you sure it was enabled before running stop?

There is nothing in your description which should disable the service, the only way would be through `systemd's disable`. So, since you say this was never run I would assume the image you installed had the daemon disabled by default.

---

<div class="post-metadata">

**Author:** ![lmrogp](https://avatars.discourse-cdn.com/v4/letter/l/c4cdca/32.png) [@lmrogp](https://hub.mender.io/u/lmrogp)\
**Post date:** [August 10, 2021, 3:39pm UTC](https://hub.mender.io/t/standalone-deployment-the-mender-client-daemon/3986/3 "2021-08-10T15:39:12Z")

</div>

I had interactively installed `mender-client` on the system, but I don’t specifically remember checking the service status before doing the stop. So I agree the best explanation is that it was not enabled to begin with.