mirror of
https://github.com/juanfont/headscale.git
synced 2026-10-23 23:06:49 +09:00
docs: note the audit-log shutdown lasts until tailscale up
Clients that opt out of logging themselves hit it whatever logtail.enabled says.
This commit is contained in:
1 parent
da6c8f9dd3
commit
29e18d80b4
1 file changed
+2
-1
+2
-1
@@ -208,7 +208,8 @@ applied by a client once it successfully connected with Headscale. See the confi
|
|||||||
|
|
||||||
Do not grant the `https://tailscale.com/cap/data-plane-audit-logs` node attribute while `logtail.enabled` is `false`. A
|
Do not grant the `https://tailscale.com/cap/data-plane-audit-logs` node attribute while `logtail.enabled` is `false`. A
|
||||||
client with log submission disabled treats this attribute as "the tailnet requires logging" and turns itself off, as
|
client with log submission disabled treats this attribute as "the tailnet requires logging" and turns itself off, as
|
||||||
`tailscale down` would.
|
`tailscale down` would. It stays off until the attribute is removed and `tailscale up` is run. A client started with
|
||||||
|
`TS_NO_LOGS_NO_SUPPORT=true` or `--no-logs-no-support` reacts the same way, whatever `logtail.enabled` says.
|
||||||
|
|
||||||
Alternatively, logging can also be disabled on the client side. This is independent of Headscale and opting out of
|
Alternatively, logging can also be disabled on the client side. This is independent of Headscale and opting out of
|
||||||
client logging disables log submission early during client startup. The configuration is operating system specific and
|
client logging disables log submission early during client startup. The configuration is operating system specific and
|
||||||
|
|||||||
Reference in new issue
Block a user