Bug 8187 - xinit.log can become very large, consuming all space
Summary: xinit.log can become very large, consuming all space
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Agent (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
Depends on:
Reported: 2023-07-11 09:28 CEST by Pierre Ossman
Modified: 2023-07-11 13:22 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2023-07-11 09:28:25 CEST
We redirect output for all applications in the session to the file xinit.log. This is a direct equivalent to how a local login redirects output to ~/.xsession-errors.

Unfortunately, there is no management of what happens if there is a log data, e.g. for very long-lived sessions, or misbehaving applications. The log cannot be rotated as applications need to reopen the file for that to work, and no applications are prepared to reopen their stdout/stderr.

If the file grows too large, it might fill up the filesystem it is on (which might be /), which in turn likely causes all sorts of issues. If there is no quota set up, then other users, or the entire system, might stop working correctly.

Modern systems have switched away from ~/.xsession-errors to journald, and the size issue might be one reason for that.

Note You need to log in before you can comment on or make changes to this bug.