Bug 107671 - cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
Summary: cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: cdrtools
Version: rawhide
Hardware: i686
OS: Linux
medium
low
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-21 21:43 UTC by Dave Maley
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-10-24 14:24:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Maley 2003-10-21 21:43:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031014

Description of problem:
When using cdrecord as a normal user I see the following warning messages:

> cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
> cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
> cdrecord: WARNING: This causes a high risk for buffer underruns.

I changed /usr/bin/cdrecord to suid root, as suggested in the man page:

     chown root /usr/bin/cdrecord
     chmod 4711 /usr/bin/cdrecord

... however this didn't help.

There don't seem to be any actually problems burning CD's as a normal user, just
the warning messages.  

These warnings are not present when using cdrecord as the root user.


Version-Release number of selected component (if applicable):
cdrecord-2.01-0.a19.1

How reproducible:
Always

Steps to Reproduce:
1. as normal user: cdrecord -v -dao -pad -eject <image.iso>
2.
3.
    

Actual Results:  CD burned fine, but warning messages are displayed

Expected Results:  no warnings

Additional info:

Comment 1 Harald Hoyer 2003-10-24 14:24:14 UTC
just warnings that it cannot get into the realtime scheduler... please report
this upstream to the author of cdrecord


Note You need to log in before you can comment on or make changes to this bug.