[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


Hi Daniel,

On Thursday 17 April 2008 02:33, Daniel Hahler wrote:
> ** Attachment added: "debdiff for Hardy"
>    http://launchpadlibrarian.net/13530861/boinc_5.10.45-1ubuntu1.dsc.diff

     if [ ! -x "`which ionice 2>/dev/null`" ]; then
       log_progress_msg "ionice not found,"
     else
-      ionice -c 3 -p $pid
-      log_progress_msg "idle,"
+      if ionice -c 3 -p $pid 2>/dev/null; then
+        log_progress_msg "idle,"
+      else
+        log_progress_msg "idle not allowed,"
+      fi
     fi

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.

Cheers,
-- 
Frank S. Thomas <fst at debian.org>           PGP public key ID: 0xDC426429
Debian Developer                            finger fst/key at db.debian.org


** Attachment added: "unnamed"
   http://launchpadlibrarian.net/13535096/unnamed

-- 
boinc-client fails to install/start, if ioprio_set is not allowed
https://bugs.launchpad.net/bugs/218468
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 mailing list