Classic confinement request: sysx

store-requests classic-confinement
1

  • name: sysx

  • description: sysx is a CLI-based system inspection and information utility that displays CPU usage, memory usage, disk usage, uptime, and hardware-related details. It is designed to provide accurate host-level system information in a read-only manner.

  • snapcraft: PRIVATE

  • upstream: PRIVATE

  • upstream-relation: The snap publisher (ayushrajsharma) is the original author and maintainer of the upstream project.

  • supported-category: system-tools

  • reasoning: sysx requires unrestricted read access to host system information paths such as /proc and /sys to collect accurate CPU, memory, and hardware metrics. These access patterns are not fully achievable under strict confinement, as strict confinement restricts access to several host-level kernel-exported interfaces that sysx depends on for correct functionality. While some information can be accessed using existing interfaces, they are not sufficient to reliably gather all required system metrics across different distributions and environments.

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

2

This request has been added to the queue for review by the @reviewers team.

3

There are many other similar snaps like htop & btop etc that use various interfaces like system-observe and hardware-observe etc so it should be possible for sysx to be strictly confined.

Also it does not fit within one of the supported categories for classic confinement so does not meet the requirements for classic confinement.

Please try making it strictly confined, feel free to open another thread here if you run into difficulty.

1 Like
4

Hello @ayushrajsharma and a Happy New Year :santa:

As also stated by @alexmurray, the snap is not a good candidate for classic confinement (#reject).

If you need further assistance with the snap, feel free to ask :slight_smile: