Look like it didn't land in the 4.1 as it was supposed to based on the upstream
milestone.
The bug is still open.
Feel free to circle back with upstream if needed.
I'll mark this as "incomplete" for now.
Regards,
Eric
** Changed in: sosreport (Ubuntu)
Status: Triaged => Incomplete
--
This bug is now part of the upstream 4.1 milestone;
https://github.com/sosreport/sos/milestone/11
Will keep this case mark as 'triage' for now.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually... on second thought a command-line option may be unavoidable.
If sosreport were to explicitly set a io policy, it might end up
overriding what the operator might specify via ionice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Andreas,
I can understand upstream's approach: sosreport should just do its job, and
tuning should be up to the administrator. Having said that, given the type of
tool sosreport is and the circumstances it tends to be used in, I think that we
could offer a better user experience if
Thanks for filing this bug in Ubuntu, and the upstream one as well.
Upstream doesn't seem very keen in making such a change for the general
case. Maybe if you could propose a command-line option that would add
it?
** Bug watch added: github.com/sosreport/sos/issues #1844
Thanks for filing this bug in Ubuntu, and the upstream one as well.
Upstream doesn't seem very keen in making such a change for the general
case. Maybe if you could propose a command-line option that would add
it?
** Bug watch added: github.com/sosreport/sos/issues #1844