best way to background the process?? #7

Closed
opened 2025-12-29 01:19:37 +01:00 by adam · 2 comments
Owner

Originally created by @outbackdingo on GitHub (Jun 17, 2021).

So running ./headscale serve & does launch the system and allow client to reg/communicate until you drop that ssh session, then it appears to somehow hangup, i noticed this after rebooting a client and re-running tailscale up .... no joy it jjust sat there.

after i logged back into the headscale vm, and killed and restarted headscale serve, then the cleint would auth again.
So... I think we need a systemd unit for headscale

Originally created by @outbackdingo on GitHub (Jun 17, 2021). So running ./headscale serve & does launch the system and allow client to reg/communicate until you drop that ssh session, then it appears to somehow hangup, i noticed this after rebooting a client and re-running tailscale up .... no joy it jjust sat there. after i logged back into the headscale vm, and killed and restarted headscale serve, then the cleint would auth again. So... I think we need a systemd unit for headscale
adam closed this issue 2025-12-29 01:19:37 +01:00
Author
Owner

@ptman commented on GitHub (Jun 23, 2021):

Have you tried running it in screen/tmux? But a .service doesn't have to be hard:

[Unit]
Description=headscale
After=network.target

[Service]
ExecStart=/path/to/headscale serve

[Install]
WantedBy=multi-user.target
@ptman commented on GitHub (Jun 23, 2021): Have you tried running it in screen/tmux? But a .service doesn't have to be hard: ```ini [Unit] Description=headscale After=network.target [Service] ExecStart=/path/to/headscale serve [Install] WantedBy=multi-user.target ```
Author
Owner

@outbackdingo commented on GitHub (Jun 23, 2021):

that actually worked :)

@outbackdingo commented on GitHub (Jun 23, 2021): that actually worked :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#7