k3b: cdrecord will be run without root privileges

[Paul Smith]

On 7/30/06, Steven Pasternak <stevenp500 at bellsouth.net> wrote:
> >> When I start k3b, I get a warning message saying:
> >>
> >> «cdrecord will be run without root privileges
> >> It is highly recommended to configure cdrecord to run with root
> >> privileges. Only then cdrecord runs with high priority which increases
> >> the overall stability of the burning process. Apart from that it
> >> allows changing the size of the used burning buffer. A lot of user
> >> problems could be solved this way. This is also true when using SuSE's
> >> resmgr.
> >> Solution: Use K3bSetup to solve this problem.»
> >>
> >> How can I solve that? I have tried
> >>
> >> $K3bSetup
> >> bash: K3bSetup: command not found
> >> $
> >>
> >> and
> >>
> >> $ k3bsetup
> >> bash: k3bsetup: command not found
> >> $
> >
> > Solved meanwhile with:
> >
> > chmod 4711 /usr/bin/cdrecord
> >
> Why???????? That is only needed on linux < 2.6.9 (FC1-FC2). On the newer
> (FC3+) versions, cdrecord only needs normal privileges. That is why
> k3bsetup is gone; it doesn't apply to Fedora anymore (unless you are on
> FC1 or FC2; not recommended).

Thanks, Rex and Steven. I am on FC5. By doing

chmod 4711 /usr/bin/cdrecord

solved the problem with the mentioned warning given by k3b. However,
k3b was unable to record or blank CD-RWs, and furthermore with
cdrecord, I got

"Cannot get mmap for 4198400 Bytes on /dev/zero"

This problem had already been discussed here before:

http://marc.theaimsgroup.com/?l=fedora-list&m=114760874326564&w=2

Finally, after having done some searches on Google, I got the
following workaround:

/etc/security/limits.conf:
* hard memlock unlimited
* soft memlock unlimited

which really works in my case. See also

http://www.gatago.com/linux/redhat/9984299.html

Paul