Skip to content

kit-423-frankendancer-logs-are-not-truncated-which-causes-storage-to#93

Closed
dantedelucia wants to merge 0 commit into
mainfrom
kit-423-frankendancer-logs-are-not-truncated-which-causes-storage-to
Closed

kit-423-frankendancer-logs-are-not-truncated-which-causes-storage-to#93
dantedelucia wants to merge 0 commit into
mainfrom
kit-423-frankendancer-logs-are-not-truncated-which-causes-storage-to

Conversation

@dantedelucia
Copy link
Copy Markdown
Contributor

The path needs to be set as "" in order to not log to a file. INFO seemed to be the recommended config for journalctl logging of stderr.

@linear
Copy link
Copy Markdown

linear Bot commented Jun 16, 2025

@dantedelucia dantedelucia changed the title Journalctl support for firedancer kit-423-frankendancer-logs-are-not-truncated-which-causes-storage-to Jun 16, 2025
@dantedelucia dantedelucia force-pushed the kit-423-frankendancer-logs-are-not-truncated-which-causes-storage-to branch from 54e0a3a to 31e1262 Compare June 16, 2025 18:20
@dantedelucia dantedelucia force-pushed the kit-423-frankendancer-logs-are-not-truncated-which-causes-storage-to branch from 31e1262 to 0535cb5 Compare June 20, 2025 00:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant