Bug 175687 - pthread_setschedparam(3) may fail for undocumented reason (EPERM)
Summary: pthread_setschedparam(3) may fail for undocumented reason (EPERM)
Status: Open
Alias: None
Product: Documentation
Classification: Unclassified
Component: Manual Pages (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-30 02:30 UTC by Mikhail T.
Modified: 2018-04-11 21:15 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail T. 2013-01-30 02:30:00 UTC
	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.
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:00 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped