Hi,

I've just upgraded to cdrtools 2.01a16 after upgrading to linux 2.4.21.

The owner.group of cdrecord is set to root.disk, its set uid bit is set.

But now I get these annoying errors when running cdrecord as a mortal user:

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

A look at the output of ps showed me that cdrecord doesn't run with root priviledges:

  F   UID   PID  PPID PRI  NI   VSZ  RSS WCHAN  STAT TTY        TIME COMMAND
100   501 11012  3153  10   0 17900 17900 ide_do DL  pts/2      0:00 cdrecord -dummy 
dist-files/image.iso
040   501 11049 11012   9   0 17900 17900 nanosl S   pts/2      0:00 cdrecord -dummy 
dist-files/image.iso

Now I've downgraded to cdrecords 2.0 again and everything works fine again, ps output:

  F   UID   PID  PPID PRI  NI   VSZ  RSS WCHAN  STAT TTY        TIME COMMAND
100     0 13479  3153   9   0 17864 17864 ide_do DL  pts/2      0:00 cdrecord -dummy 
dist-files/image.iso
140     0 13516 13479   9   0 17864 17864 nanosl S   pts/2      0:00 cdrecord -dummy 
dist-files/image.iso


What can I do to for a recent cdrecord to setuid(0) again?

Thanks for any help.

        Carsten


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to