Srinivas G. wrote:
> > Yes, subject to certain restrictions, which are detailed in the
> > sched_setscheduler(2) manpage.
> >
> > In particular, a non-privileged process cannot set the real-time
> > priority higher than its RLIMIT_RTPRIO setting. You can change this
> > with an "rtprio" entry in /etc/security/limits.conf (settings are
> > applied on login, so changes won't affect existing login sessions).
> >
> > Privilege is determined by the CAP_SYS_NICE capability.
>
> Thanks Glynn.
>
> I have tried to set the RLIMIT_RTPRIO to 100 through
> /etc/security/limits.conf. It was not defined previously, so I have
> defined in the following way.
>
> domain type item value
> #@srinivasg soft rtprio 100
First, as Ben says, you must uncomment the line. Second, you may also
need to set the hard limit. You can use "ulimit -a" (or -aH) to check
the actual limits.
--
Glynn Clements <glynn@xxxxxxxxxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux Assembler]
[Git]
[Kernel List]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[Yosemite Campsites]
[Yosemite News]
[GCC Help]