Add top-like monitoring tool

[ben-grande]

Requires: QubesOS/qubes-core-agent-linux#550

---

which I don't know how to indirectly timeout the subprocess created by run_service_for_stdio.

run_service_for_stdio can't do that for you, but run_service can - it returns subprocess instance on which you can wait yourself, including own timeout handling (like proc.communicate(timeout=...)).

I did that, but it seems that it is difficult to limit the amount of bytes that can be read as proc.communicate(timeout=1) is a blocking operation as well as proc.stdout.read(2)

To ensure a domU doesn't fill up Dom0 memory that is being assigned to untrusted_mem, something like this would have to be done: https://stackoverflow.com/a/34114767, unless someone knows a better solution.

[marmarek]

is a blocking operation as well as proc.stdout.read(2)

Do you mean read() hangs for you? Maybe the service waits for something before starting to output any data (doesn't look like it based on the other PR...).

[ben-grande]

Not the service by default, I prepended sleep to awk to test if a DomU could hang operation on Dom0 and if this is a valid concern.

…

On Tue, Jan 28, 2025, 12:25 PM Marek Marczykowski-Górecki < ***@***.***> wrote: is a blocking operation as well as proc.stdout.read(2) Do you mean read() hangs for you? Maybe the service waits for something before starting to output any data (doesn't look like it based on the other PR...). — Reply to this email directly, view it on GitHub <#333 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCE2O4LDOXXM2LA43ENCLQ32M5SKPAVCNFSM6AAAAABWAFNTCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJYG4ZDGNBUG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>