[systemd-devel] Services started realtime exit with 214

Barry Scott barry.scott at onelan.co.uk
Mon Jul 11 04:40:15 PDT 2011


I am trying to run services realtime with systemd on Fedora 15.

Here is the Service section that I think we need to do this.

[Service]
StandardOutput=syslog
WorkingDirectory=/data/data/logs

LimitCORE=infinity
LimitRTPRIO=2
LimitRTTIME=60000000
CPUSchedulingPolicy=rr
CPUSchedulingPriority=1

ExecStartPre=-/bin/plymouth quit --retain-splash
ExecStart=/usr/bin/Xorg :0 -noreset -nolisten tcp -background none vt1 -dpi 75 -logfile /data/data/logs/screen-server.log -dumbSched -config /etc/onelan/ntb/x.conf

# systemctl status screen.service
screen.service - Screen arbitration server for the display
          Loaded: loaded (/etc/systemd/system/screen.service)
          Active: failed since Mon, 11 Jul 2011 11:55:45 +0100; 19min ago
         Process: 990 ExecStart=/usr/bin/Xorg :0 -noreset -nolisten tcp -background none vt1 -dpi 75 -logfile /data/data/logs/screen-server.log -dumbSched -config /etc/onelan/ntb/x.conf (code=exited, status=214/SETSCHEDULER)
         Process: 988 ExecStartPre=/bin/plymouth quit --retain-splash (code=exited, status=214/SETSCHEDULER)
          CGroup: name=systemd:/system/screen.service

Why is the sched_scheduler call failing?

Do we have to configure something else to get this working like cgroup stuff?

Barry


More information about the systemd-devel mailing list