Scott Yeager

Thanks for the details @AbdelrahmanElawady. What you wrote can explain why this case fails to be reported as an update by Zos: ``` Disk -> Disk (with description) ``` But...

Ah yes, makes sense now @AbdelrahmanElawady. I had forgotten that the disk and VM are separate workloads, and that the client is looking to confirm the version change on both....

Sure, happy to! PS, I didn't see an issue form type for documentation.

It seems that maybe the solution didn't work as intended. A farmer is reporting they still see the following on screen when a node with Zos 3.8.4 shuts down: 

Still seeing cases of the ugly shutdown screen. Reported today:  Could you have another look at this, @MarioBassem?

> * ZOS is programmed to `clean up` any cached files that are not used accessed for 3 days. So we can warm up the cache but then it gets...

Looks like an issue with the device going into some kind of power saving mode. You can try enabling wake lock in the settings, or look into some further measures...

You can also add `user:aid_inet` (replace with your username) into the "Privileged users" section of the container configuration.

Since we've established that performance on Yggdrasil is out of our control and we aren't currently pursuing replacing it with a more performant solution, I think we should revisit this...

Thanks guys. I'll try compiling a version without that bit for my own use for now. A run time option would be great, especially if it's easily toggled from Cadence...