> For the complete documentation index, see [llms.txt](https://docs.noports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noports.com/installation/advanced-installation-guides/device-installation-sshnpd/standalone-binaries.md).

# Running without systemd

The NoPorts daemon doesn't have to be run by systemd

Once NoPorts is installed with a `/etc/noports/sshnpd.yaml` config and an atKeys file all that's needed to start the daemon is to run `sshnpd` .

But... without systemd there's nothing to restart `sshnpd` if it exits, and there's nothing capturing logs (and compressing, rotating and pruning them).

At the most basic level a simple script will restart the daemon if it fails:

```bash
#!/bin/bash
BACKOFF_INTERVAL=10
while true; do
  sshnpd
  sleep "$BACKOFF_INTERVAL"
done
```

Whatever runs `sshnpd` should be some kind of background task (so it doesn't exit when the session launching it is disconnected). For example redirect logs and run in background with:

```
nohup sshnpd > sshnpd.log 2> sshnpd.err < /dev/null &
```

A similar effect can be achieved by running `sshnpd` inside a terminal multiplexer such as [GNU Screen](https://www.gnu.org/software/screen/) or [Tmux](https://en.wikipedia.org/wiki/Tmux).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.noports.com/installation/advanced-installation-guides/device-installation-sshnpd/standalone-binaries.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.