2 ms·
Not really related to this solution specifically but: # wait for tailscaled to settle sleep 2 This is going to break one day. They're already using syst
by viraptor 6y ago
Not really related to this solution specifically but:
# wait for tailscaled to settle
sleep 2
This is going to break one day. They're already using systemd units - why not make tailscale notify when it's done with the startup? We have better tools than old initd - let's use them.
- joshspankit 6y agoMy thought also. As well, maybe a little over-picky, but I’m not a fan of “22” in the firewall config. I assume there’s something like config.ssh.port
- arianvanp 6y agoThere is a `services.openssh.openFirewall = true` option that will open ports for all listener directives for you
- arianvanp 6y agoYes that would indeed fix this. Can use https://pkg.go.dev/github.com/coreos/go-systemd/daemon https://pkg.go.dev/github.com/coreos/go-systemd/daemon for this. `go-systemd` is already an indirect dependency of `tailscale` so this doesn't contribute to dependency footprint either if that's a concern. Perhaps we should open a ticket (or a pull-request?)
- xena 6y agoAuthor of the post here. Yes, I'm aware. I've added systemd-notify support to git main, however it's not been released yet. As soon as it is released (and it percolates down to nixpkgs) that hack will be irrelevant and can be purged.