Date: Tue, 29 Jan 2013 21:27:24 -0500 (EST) From: "Mikhail T." <mi@aldan.algebra.com> To: FreeBSD-gnats-submit@freebsd.org Subject: docs/175687: pthread_setschedparam(3) may fail for undocumented reason (EPERM) Message-ID: <201301300227.r0U2ROdp093445@narawntapu.narawntapu> Resent-Message-ID: <201301300230.r0U2U0Aw083749@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 175687 >Category: docs >Synopsis: pthread_setschedparam(3) may fail for undocumented reason (EPERM) >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 30 02:30:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Mikhail T. >Release: FreeBSD 9.1-PRERELEASE amd64 >Organization: Virtual Estates, Inc. http://sybpipe.com/ >Environment: >Description: The pthread_setschedparam(3) manual page lists the following possible reasons for the function's failure: The pthread_setschedparam() function will fail if: [EINVAL] Invalid value for policy. [ENOTSUP] Invalid value for scheduling parameters. [ESRCH] Non-existent thread thread. However, the function may also fail -- with EPERM -- if an attempt is made to alter the scheduling policy of a thread. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301300227.r0U2ROdp093445>