On Wed, Feb 27, 2013 at 10:00 PM, Clark Williams <williams@xxxxxxxxxx> wrote: > Well this is a new one on me. Some questions: > > Do you have SELinux running? No SELinux is disabled > > Are there any files in /etc/security/limits.d other than the one you put > there? > Yes there are: root@overo:/etc/security# ls -l total 40 -rw-r--r-- 1 root root 4620 Feb 26 2013 access.conf -rw-r--r-- 1 root root 3635 Feb 26 2013 group.conf -rw-r--r-- 1 root root 1825 Feb 26 2013 limits.conf drwxr-xr-x 2 root root 4096 Feb 26 2013 limits.d -rw-r--r-- 1 root root 1442 Feb 26 2013 namespace.conf drwxr-xr-x 2 root root 4096 Feb 26 2013 namespace.d -rwxr-xr-x 1 root root 1020 Feb 26 2013 namespace.init -rw-r--r-- 1 root root 2980 Feb 26 2013 pam_env.conf -rw-r--r-- 1 root root 2180 Feb 26 2013 time.conf > Other than that I can't think of a reason why sched_setscheduler() > would fail as root. -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
