| LinHES Forums http://forums.linhes.org/ |
|
| ionice & LinHes http://forums.linhes.org/viewtopic.php?f=25&t=24816 |
Page 1 of 1 |
| Author: | thekingofspain [ Wed Jan 23, 2019 2:35 am ] |
| Post subject: | ionice & LinHes |
Looking for some advice on setting up ionice for the following binaries: mythbackend, mythfrontend, mythcommflag My limited understanding of how to properly use ionice is to leverage the /user/local/bin directory, a wrapper script, and symlink. /usr/local/bin/nicer-2.1 Code: #! /bin/sh ionice -c 2 -n 1 nice -n 20 /usr/bin/"${0##*/}" "$@" symlink script to binaryName. Code: ln -s nicer-2.1 /user/local/bin/binaryName ionice is only binding to the mythcommflag binary, probably due to how the other binaries are being called/referenced. I made another script for the /usr/LH/bin directory and created a link for LinHES-start seeing if that would trigger ionice on mythfrontend. The result was the LinHES-start was ioniced but mythtfrontend still ran in the default ionice class. I used this approach as its seems the least obstructive method to preserve the LinHES environment; I am open to other delivery mechanisms (proceas id, sv, ...). |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|