Interesting: free and portable (no install required: just unzip and go): [WayBack] O&O ShutUp10.
Via [WayBack] Jeroen Wiert Pluimers – Google+ (which I think I got via Twitter)
–jeroen
Posted by jpluimers on 2019/08/12
Interesting: free and portable (no install required: just unzip and go): [WayBack] O&O ShutUp10.
Via [WayBack] Jeroen Wiert Pluimers – Google+ (which I think I got via Twitter)
–jeroen
Posted in Power User, Windows, Windows 10 | Leave a Comment »
Posted by jpluimers on 2019/08/12
The [WayBack] stock zabbix_agentd.conf
is about 10k and the documentation quite a bit larger, so it can take a while to figure out a setting.
I needed one to ensure that scripts could take longer to execute than the default.
Searching for a per-script setting on the server side revealed no solution, so I had to solve it on the agent side. There, a per-script setting is also impossible: there is only the global Timeout
(one word, no PascalCase like TimeOut
) setting in zabbix_agentd.conf
which is the same for Unix and Windows based Zabbix installations:
Unix: [WayBack] Zabbix Documentation 3.0 – 3 Zabbix agent (UNIX)
Parameter Mandatory Range Default Description Timeout
no 1
–30
3
Spend no more than Timeout
seconds on processing
Windows: [WayBack] Zabbix Documentation 3.0 – 9.4 Zabbix agent (Windows)
Parameter Mandatory Range Default Description Timeout
no 1
–30
3
Spend no more than Timeout
seconds on processing
In my case it was for a PowerShell script that ran twice a day to verify how recent the installations on a particular machine were. The Timeout
value needed to be at least 15
for that:
### Option: Timeout
# Spend no more than Timeout seconds on processing.
#
# Mandatory: no
# Range: 1-30
# Default:
# Timeout=3
Timeout=15
–jeroen
Posted in *nix, Monitoring, Power User, Zabbix | Leave a Comment »
Posted by jpluimers on 2019/08/12
Via [WayBack] Anyone with a hint on how to work around this: … “Please re-run this installer as a normal user instead of”… – Jeroen Wiert Pluimers – Google+
This happened for instance when trying to install Source Tree 2.x on Windows (1.9.x works fine):
[Window Title]
SourceTreeSetup-2.3.1.0.exe[Main Instruction]
Installation has failed[Content]
Please re-run this installer as a normal user instead of “Run as Administrator”.[Close]
The problem was by accident the machine got in a state to run commands without UAC approval, so the run dialog would already look have “This task will be created with administrative privileges”:
It was odd, as the machine didn’t have it enabled in the security policy (secpo.msc
):
So I did a bit more digging, bumped into [WayBack] Why does my Run dialog say that tasks will created with administrative privileges? – The Old New Thing and had one of those #facepalm moments: Explorer had crashed, and I had started it from Process Explorer, forgetting Process Explorer had an UAC token.
The solution is easy:
–jeroen
Posted in Batch-Files, Console (command prompt window), Development, Power User, Scripting, Software Development, The Old New Thing, Windows, Windows Development | Leave a Comment »