Hello,
I'm looking to create a random `wapt_update` command that will download the latest packages assigned to the computer throughout the day.
Unfortunately, it's only possible to assign a fixed value.
This would prevent network overload and distribute the load evenly.
Thank you.
random wapt_update
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Hello,
A few thoughts:
1) Since client machine startups aren't perfectly synchronized, the installation staggering happens naturally.
But in case that's not enough:
2) This task can be performed from a script on the server using `psexec \\* -u admin` or `system -p password wapt-get`...
3) We could imagine deploying a scheduled task that, when the machines start, calls a script with an infinite loop that randomly invokes the `wapt-get` command.
A few thoughts:
1) Since client machine startups aren't perfectly synchronized, the installation staggering happens naturally.
But in case that's not enough:
2) This task can be performed from a script on the server using `psexec \\* -u admin` or `system -p password wapt-get`...
3) We could imagine deploying a scheduled task that, when the machines start, calls a script with an infinite loop that randomly invokes the `wapt-get` command.
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
To my knowledge:
A download of the packages to be updated is performed when the machine starts up.
Then, the "waptupdate_task_period" parameter manages how often the WAPT client should check and download the new packages. I wonder if a random value isn't already added to this.
PC startup times are generally staggered, except when PCs are started in the morning via Wake-on-LAN.
At my place, about 70 PCs are started via Wake-on-LAN in the morning; there's a bit of a load for a few minutes, then it calms down. But since it's morning, no one notices.
Why not add a random value? But how do you find a parameter that pleases everyone?
We could, however, create a package that will write a random value for waptupdate_task_period to the wapt-get.ini file.
A value between 60 and 120 (minutes).
Simon
A download of the packages to be updated is performed when the machine starts up.
Then, the "waptupdate_task_period" parameter manages how often the WAPT client should check and download the new packages. I wonder if a random value isn't already added to this.
PC startup times are generally staggered, except when PCs are started in the morning via Wake-on-LAN.
At my place, about 70 PCs are started via Wake-on-LAN in the morning; there's a bit of a load for a few minutes, then it calms down. But since it's morning, no one notices.
Why not add a random value? But how do you find a parameter that pleases everyone?
We could, however, create a package that will write a random value for waptupdate_task_period to the wapt-get.ini file.
A value between 60 and 120 (minutes).
Simon
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Example package to apply a random value to waptupdate_task_.;
Code: Select all
# -*- coding: utf-8 -*-
from setuphelpers import *
import random
uninstallkey = []
def install():
print('installing smp-random-waptupdate_task_period')
valeur_waptupdate_task_period = random.randint(60,120)
inifile_writestring(WAPT.config_filename,'global','waptupdate_task_period',valeur_waptupdate_task_period)
