Hi,
After discussing this issue with upstream we came to the conclusion that
reverting this is the best option as it is possible to start programs
trough vmtoolsd and they would also run with a nice level of -20.
Upstream will fix this issue in a sane way.
I've reopened the bug.
Sorry,
Bernd
On Mon, Mar 9, 2020 at 2:23 AM Bernd Zeimetz wrote:
>
> Hi Aron,
>
> which nice level do you suggest? -10?
>
I'd suggest -20, since vmtoolsd does not consume a lot resources
itself while the highest priority would give it better chance to deal
with watchdog stuff.
Regards,
Aron
Hi Aron,
which nice level do you suggest? -10?
Bernd
On 3/8/20 10:02 AM, Aron Xu wrote:
> Package: open-vm-tools
> Severity: wishlist
>
> I've been experiencing false alarms of VM monitoring for those who
> runs very CPU intensive tasks for long time (i.e. several hours), and
> it seems that
Package: open-vm-tools
Severity: wishlist
I've been experiencing false alarms of VM monitoring for those who
runs very CPU intensive tasks for long time (i.e. several hours), and
it seems that raising the process priority of vmtoolsd will let the
watchdog work more properly. This has relaxed the s
4 matches
Mail list logo