From f911f4805129742e836e40e0785f4da62558865b Mon Sep 17 00:00:00 2001 From: Ben Hoyt Date: Thu, 10 Mar 2022 15:00:26 +0100 Subject: [PATCH] Document that "pebble logs -f" only follows currently-running services It would be quite an significant refactoring to have "pebble logs -f" subscribe to new services being started and wire that through, so for now at least, just document the current behaviour. It seems unlikely to affect people in practice, as the service(s) you're debugging will likely be running. --- cmd/pebble/cmd_logs.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmd/pebble/cmd_logs.go b/cmd/pebble/cmd_logs.go index 68aa01b62..2929e2d94 100644 --- a/cmd/pebble/cmd_logs.go +++ b/cmd/pebble/cmd_logs.go @@ -42,7 +42,7 @@ type cmdLogs struct { } var logsDescs = map[string]string{ - "follow": "Follow (tail) logs for given services until Ctrl-C pressed.", + "follow": "Follow (tail) logs for given services until Ctrl-C is\npressed. If no services are specified, show logs from\nall services running when the command starts.", "format": "Output format: \"text\" (default) or \"json\" (JSON lines).", "n": "Number of logs to show (before following); defaults to 30.\nIf 'all', show all buffered logs.", }