From: Manish Katiyar <mkatiyar@gmail.com>
To: "Srinivas G." <srinivasg@esntechnologies.co.in>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Unable set the priority for a pthread through pthread_setschedparam
Date: Tue, 3 Feb 2009 13:41:55 +0530 [thread overview]
Message-ID: <ea11fea30902030011g54b997e9vb9a1828bd350a9ac@mail.gmail.com> (raw)
In-Reply-To: <F5BA82141F7AA94885B9643C77EEA5F2103C8A@mail.esntechnologies.co.in>
On Tue, Feb 3, 2009 at 11:57 AM, Srinivas G.
<srinivasg@esntechnologies.co.in> wrote:
>> The man page says it all
>>
>> !EPERM!
>> the calling process does not have superuser
>> permissions
>>
>> you cannot unless you have superuser permissions.
>>
>
> Dear Manish,
>
> Thanks for the information.
>
> I have seen the man pages and find the following.
>
> EPERM The caller does not have appropriate privileges to set the
> specified
> scheduling policy and parameters.
>
> I have tried to set the super user permissions to a normal user through
> user and groups. However I found there are lot of different groups
one with id 0 .. see /etc/group
Thanks -
Manish
> exists like
> adm
> apache
> avahi
> bin
> daemon
> dbus
> dip
> etc.
>
> Which groups shall I need to select for setting the super user
> permissions?
>
> Thanks in advance.
>
> Thanks and Regards,
> Srinivas G
>
>
next prev parent reply other threads:[~2009-02-03 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 4:48 Unable set the priority for a pthread through pthread_setschedparam Srinivas G.
2009-02-03 5:44 ` Manish Katiyar
2009-02-03 6:27 ` Srinivas G.
2009-02-03 8:11 ` Manish Katiyar [this message]
2009-02-04 1:49 ` Glynn Clements
2009-02-04 6:31 ` Srinivas G.
2009-02-04 15:32 ` ben
2009-02-04 23:07 ` Glynn Clements
2009-02-05 4:06 ` Srinivas G.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea11fea30902030011g54b997e9vb9a1828bd350a9ac@mail.gmail.com \
--to=mkatiyar@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=srinivasg@esntechnologies.co.in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).