Skip to content

Improve warnings and invalid values for systemd - #572

Merged
SJrX merged 2 commits into
242.xfrom
feat/565-severity
Oct 27, 2026
Merged

SJrX merged 2 commits into
242.xfrom
feat/565-severity

Conversation

@SJrX

@SJrX SJrX commented Oct 25, 2026

Copy link
Copy Markdown
Owner

No description provided.

@github-actions

Copy link
Copy Markdown

Unit Test Results (grammar engine true)

1 917 tests   1 917 ✅  1m 15s ⏱️
  528 suites      0 💤
  528 files        0 ❌

Results for commit db9fc63.

@github-actions

Copy link
Copy Markdown

Unit Test Results (grammar engine false)

1 917 tests   1 917 ✅  1m 23s ⏱️
  528 suites      0 💤
  528 files        0 ❌

Results for commit db9fc63.

SJrX and others added 2 commits October 27, 2026 16:19
Add warnings (not errors) for values systemd still accepts but warns
about, so they are no longer silently treated as fine:

- StandardOutput=/StandardError= syslog and syslog+console (obsolete,
  systemd uses journal / journal+console)
- the "!!" prefix on Exec*= lines (no longer supported, ignored)
- unknown escape sequences in Exec*= arguments (systemd keeps the
  backslash and logs a warning)
- PIDFile= and socket paths under /var/run (systemd rewrites to /run)
- KillMode=none (unsafe)
- User=nobody and SocketUser=nobody (systemd logs "not safe" at notice
  level, so this one is a weak warning)
- Address=/Peer= without a prefix length, and unmasked AllowedIPs=
- deprecated boolean forms of IPMasquerade= and IPv4LL=

Each message says what systemd does and what to write instead.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
)

Values that systemd's parser accepts but that are rejected or dropped at
unit or container start are errors again:

- unknown RestrictFileSystems= filesystem names (dropped by the BPF
  restrict-fs code, so the entry neither allows nor denies anything)
- nspawn Bind=/BindReadOnly= with unknown mount options (container fails
  to start)
- nspawn AmbientCapability=all (refused by systemd-nspawn)
- traffic-control limits networkd refuses (e.g. ETS bands above 15, GRED
  and Xfrm limits)

nspawn SystemCallFilter= entries with "~" after the first word are
silently ignored by systemd-nspawn and now get a warning.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@SJrX
SJrX merged commit 3eaed8b into 242.x Oct 27, 2026
3 checks passed
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