[Bug 218468] Re: boinc-client fails to install/start, if ioprio_set is not allowed
Frank S. Thomas
fst at debian.org
Thu Apr 17 07:55:56 UTC 2008
On Thursday 17 April 2008 02:33, Daniel Hahler wrote:
> ** Attachment added: "debdiff for Hardy"
if [ ! -x "`which ionice 2>/dev/null`" ]; then
log_progress_msg "ionice not found,"
- ionice -c 3 -p $pid
- log_progress_msg "idle,"
+ if ionice -c 3 -p $pid 2>/dev/null; then
+ log_progress_msg "idle,"
+ log_progress_msg "idle not allowed,"
If ionice fails does this always means that "ioprio_set" is not allowed? If
the answer to this question is no, I would rather suggest to echo a more
generic message like "ionice failed," or something similar.
If you want to, you can commit this into boinc's trunk.
Frank S. Thomas <fst at debian.org> PGP public key ID: 0xDC426429
Debian Developer finger fst/key at db.debian.org
** Attachment added: "unnamed"
boinc-client fails to install/start, if ioprio_set is not allowed
You received this bug notification because you are a member of Debian
BOINC Maintainers, which is subscribed to boinc in ubuntu.
More information about the pkg-boinc-devel