2 Questions (making config for runit on Void Linux)

[MeganerdNL]

I'm making a configuration for runit (Void Linux). I have been successful in creating a runit service on basis of the systemd service provided in this project, including a script after stopping the service to reset to default via ectool.

2 questions remain:

1. Why is the fw-fancontrol-suspend needed? Is see that it pauses the fw-fanctrl program before suspend and that it resumes after. I have made a script for elogind (part of replacing systemd) to do the exact same thing successfully, but I'm unsure why this is needed, are there crashes reported? It seems to go into and out of suspend fine without this (on a Framework Laptop 16). Is it also needed for hibernate?
2. What does --no-post-install actually do? I don't quite understand what the script actually does, Does it have something with old installs? Not sure. --no-pre-uninstall seems the opposite, is that right?

I'll be happy to share the service files for runit (and the elogind files for suspend) if you like and you are welcome to incorporate them if you like.

[leopoldhub]

Hi, thank you for your interest in the project!

To answer your questions:

1. Suspending the fan control via the fw-fanctrl pause command instead of stopping the process allows the user to still get the service informations (fw-fanctrl print all), set the selected profile, list available profiles, etc...

2. The no-pre-uninstall and no-post-install disable the scripts responsible for completing, uninstalling/installing, and stopping/starting the systemd services before uninstallation / after installation.

In your case, if you do not want systemd services, you should use them.

I'll be happy to share the service files for runit (and the elogind files for suspend) if you like and you are welcome to incorporate them if you like.

Sure, we would gladly accept this contribution!

[MeganerdNL]

Thank you for your answers. 2. I understand. It did it with --no-post-install

But 1... I suspect I totally misunderstand what 1. does: I'm not on a systemd system.. I'm under the impression that fw-fancontrol-suspend is run before (pre) and after (post) suspending the entire system...

Why would anybody be interested in doing any command if the system is suspended? If it's suspended it's not even possible to issue fw-fanctrl print all. And after suspend the service is started anyway. At least this works perfectly on runit.

Could you be so kind to explain because I'm confused. I will put my files on soon, I will let you know.

[leopoldhub]

I'm not on a systemd system.. I'm under the impression that fw-fancontrol-suspend is run before (pre) and after (post) suspending the entire system...

My bad, I misunderstood your question.

We did it this way because we could not simply kill the systemd service when the laptop goes to sleep or stop/restart it at the time.

If you use an other system, feel free to not use this method if compatible.

[MeganerdNL]

Thanks, I get it! The runit files are here: https://github.com/MeganerdNL/fw-fanctrl-runit-files Feel free to link to it or use the files.

Wonderful program, thanks!