Linux packages updated on shutdown?

[Houg]

Hello everyone,

Still testing WAPT to manage our Linux workstations, I continue to have questions.
Unfortunately, I'm finding very little documentation on the Linux version (behavior, packages, explanations, agent behavior, etc.) compared to the Windows version.
The only available resource is: https://www.wapt.fr/apidoc/wapt-2.5/linux/index.html

. I currently have an Ubuntu 22.04 LTS workstation with its agent, which correctly appears in the console – Self-service GUI installed (thanks to Denis's answer in another of my posts).

When I create/update a package: it seems to work if I "force" the update on the workstation (via the console or command line), but I can't find anywhere how to automatically update the workstation when it shuts down. I
want to achieve the same behavior as Windows with Waptexit.

Furthermore, in the console, I've noticed that if my packages are for "ubuntu" or, for example, "debian_based" operating systems, they don't appear if the "linux" filter is applied. Only packages for "linux" are visible.

Thank you in advance for your help.

Wapt client Linux - Ubuntu 22.04 LTS: 2.5.4.15342
Wapt Enterprise Server (on a Linux server): WAPT Server version: 2.5.4.15342
Wapt Console (on Windows): 2.5.4.15342

[dcardon]

Hi Alexis,

it's possible to add a `wapt-get -u upgrade` command on shutdown using systemd, but the waptexit interface won't be displayed (we haven't yet managed to get it working on the waptexit graphical buffer).

You can take inspiration from the systemd option provided here: https://opensource.com/life/16/11/runni ... down-linux.

Another parameter to consider in wapt-get.ini is `waptupgrade_task_period`, which forces regular upgrades (basically, it runs a `wapt-get upgrade` every few hours). However, you must properly configure the `impacted_process` values; otherwise, the upgrades might crash applications rather abruptly during updates.

We're interested in getting more feedback on the Linux side of things, so we welcome any customer feedback !

Best regards,

Denis

[Houg]

Thanks for the quick reply.

I specifically want to avoid "waptupgrade_task_period" because if software is installed or in use, I don't know which processes are affected.
A simple program like Vim is possible, but for example, I'm going to create a package (eventually, hopefully) to deploy Nvidia CUDA (among other packages). Here, it's not just one process that's affected, and it would be too much work to list everything for all the applications.

I also can't afford to shut down an application for the user. Some of us run calculations over several weeks. So if I shut them down...

We had thought about running a command on shutdown, but I wanted to know if there was already a way to do that with WAPT. We'll look into running something when the machine shuts down.


Regarding feedback, if you'd like, we can discuss it via private message if you're interested. I could tell you what I've noted so far.

[sfonteneau]

We had thought about launching a command on shutdown, but I wanted to know if there was already a way to do it with WAPT => we'll look into launching something when the computer shuts down

Apart from systemd (the example Denis gave above), we haven't found anything better. Same problem under macOS

At a stretch, we could propose a regular update (with waptexit opening in the open session)

[Houg]

Thanks for the feedback.

We'll look into it on our end; we're still considering our options (we're not in production yet anyway ):
- either a service that installs updates on shutdown => same as Windows
- or, for example, creating a package available to the user, who would then run it themselves for updates. This way, there are no issues with a running calculation, for example. But this carries the risk that the updates might not be installed.
- Alternatively, the pop-up solution that prompts the user to update could also be good: without forcing them, but simply to inform them that updates are available.


macOS will be our next objective.