Describe the bug
On review of the gigabytes of journal files in /var/log/journal on Ubuntu 22.04 LTS, it is shown that the log data is almost exclusively coming from X11VNC. Once over the course of 24 hours the logs get to gigabyte sizes of X11VNC journal data physically and virtually, the disk and memory resources are strained to the point where X11VNC is unresponsive, requiring reboot to clear the journals from memory and restore responsiveness by X11VNC
To Reproduce
View journal files with journalctl --file (file)
Expected Behavior
Reduced logging to /var/log/journal to be on par with the volume of other services.
Add a configuration flag to disable logging or set a logging verbosity level.
Desktop (please complete the following information):
OS and version: Ubuntu 22.04 LTS
Xorg version used:
Wayland version used:
Additional context
A stop-gap is editing the journals.conf file to limit the size of the physical and virtual journals that are being filled up by X11VNC to prevent X11VNC from consuming excessive disk and memory resources. Not ideal, as logging by other services is not retained.
Describe the bug On review of the gigabytes of journal files in /var/log/journal on Ubuntu 22.04 LTS, it is shown that the log data is almost exclusively coming from X11VNC. Once over the course of 24 hours the logs get to gigabyte sizes of X11VNC journal data physically and virtually, the disk and memory resources are strained to the point where X11VNC is unresponsive, requiring reboot to clear the journals from memory and restore responsiveness by X11VNC
To Reproduce View journal files with
journalctl --file (file)Expected Behavior Reduced logging to /var/log/journal to be on par with the volume of other services. Add a configuration flag to disable logging or set a logging verbosity level.
Desktop (please complete the following information):
Additional context A stop-gap is editing the journals.conf file to limit the size of the physical and virtual journals that are being filled up by X11VNC to prevent X11VNC from consuming excessive disk and memory resources. Not ideal, as logging by other services is not retained.