FEDORA-2020-19e39ee9d7 created by salimma 2 years ago for Fedora 31
stable

Initial package; psi-notify sends alerts when your machine is becoming over-saturated

How to install

sudo dnf install --refresh --advisory=FEDORA-2020-19e39ee9d7 \*

This update has been submitted for testing by salimma.

2 years ago

This update's test gating status has been changed to 'waiting'.

2 years ago

This update's test gating status has been changed to 'ignored'.

2 years ago

This update has been pushed to testing.

2 years ago
User Icon sdgathman commented & provided feedback 2 years ago
karma

Upgrading from my prelease version, the user service was not restarted. Maybe this is correct - I don't see how systemd could reasonably restart an arbitrary bunch of user services. There is no practical problem, because the utility is so tiny.

On my desktop with 5400rpm rotating media, it complains about I/O pressure a lot. So it works as advertised.

BZ#1832623 Review Request: psi-notify - Alert when your machine is becoming over-saturated
User Icon sdgathman commented & provided feedback 2 years ago

On rebooting, psi-notify is started for every user account, whether logged in or not. Maybe having some running with no gui is why I started getting core-dumps after booting. Each user psi-notify crashes after initial load, then is restarted by systemd.

User Icon sdgathman commented & provided feedback 2 years ago

Generating a backtrace for submitting the crash report fails both for retrace server and locally.

User Icon salimma commented & provided feedback 2 years ago

@sdgathman thanks for continuing the review even after the package is created! Please file a bug and I'll take a look. It could be related to the different presets between Fedora 31 and 32 -- apparently even without using the systemd scriptlet in the spec, the service still ends up enabled.

What does systemctl --user status psi-notify say? I'll also get a Fedora 31 container or VM to test. Maybe the solution is to pre-ship a preset that disables psi-notify by default... but I'm not sure how user units get started if the user is not logged in. That is odd.

User Icon salimma commented & provided feedback 2 years ago

@sdgathman, also what's your default boot target? If it's non-graphical that could be causing the issue. I'll suggest to upstream to switch to graphical.target instead of default.target. As for being enabled by default, I suspect it could be because you had the -1.fc31 package previously installed.

User Icon sdgathman commented & provided feedback 2 years ago

Boot target is graphical. It works normally (module occasional crashes, on which systemd restarts it). It may be a feature of user services that they are started even when you aren't logged in.

$ lk psi-notify
term=xt,unicode=1
 RUSER        PID STIME TTY        TIME CMD
 root           1 May10 ?          0:07/usr/lib/systemd/systemd --switched-root --system --deserialize 29
 stuart      1242 May10 ?          0:05├/usr/lib/systemd/systemd --user
#stuart      2939 May10 ?          0:05│├/usr/bin/psi-notify
 guest       1243 May10 ?          0:05├/usr/lib/systemd/systemd --user
#guest       1276 May10 ?          0:05│└/usr/bin/psi-notify

This update can be pushed to stable now if the maintainer wishes

2 years ago

This update has been submitted for stable by bodhi.

2 years ago

This update has been pushed to stable.

2 years ago

Please login to add feedback.

Metadata
Type
newpackage
Severity
low
Karma
1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
7 days
Dates
submitted
2 years ago
in testing
2 years ago
in stable
2 years ago
BZ#1832623 Review Request: psi-notify - Alert when your machine is becoming over-saturated
0
0

Automated Test Results