# Service Operations

`rtmn` runs as a systemd service.

## Single-Instance Service

Check status:

```bash
sudo systemctl status rtmn --no-pager
```

Restart:

```bash
sudo systemctl restart rtmn
```

Stop:

```bash
sudo systemctl stop rtmn
```

Follow logs:

```bash
sudo journalctl -u rtmn -f
```

Show recent logs:

```bash
sudo journalctl -u rtmn -n 100 --no-pager
```

## Account-Isolated Services

In account-isolated installations, service names use the `rtmn-<instance>.service` format.

Check status:

```bash
sudo systemctl status "rtmn-$INSTANCE.service" --no-pager
```

Restart:

```bash
sudo systemctl restart "rtmn-$INSTANCE.service"
```

Stop:

```bash
sudo systemctl stop "rtmn-$INSTANCE.service"
```

Follow logs:

```bash
sudo journalctl -u "rtmn-$INSTANCE.service" -f
```

Show recent logs:

```bash
sudo journalctl -u "rtmn-$INSTANCE.service" -n 100 --no-pager
```

## Confirm a Healthy Start

A healthy service start sends a startup notification to the allowed Telegram chats.

Check these items:

- The systemd service is `active (running)`.
- The journal has no configuration errors.
- The startup notification arrived in every allowlisted Telegram chat.
- The audit log path is writable by the service account.