From: Lee Revell <rlrevell@joe-job.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: cd burning, capabilities and available modes
Date: Wed, 01 Dec 2004 12:05:38 -0500 [thread overview]
Message-ID: <1101920739.18170.29.camel@krustophenia.net> (raw)
In-Reply-To: <1101908433l.8423l.0l@werewolf.able.es>
On Wed, 2004-12-01 at 13:40 +0000, J.A. Magallon wrote:
> As user:
> werewolf:/store/tmp> cdrecord -dummy dev=ATAPI:1,0,0 *.iso
> ...
> cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
> cdrecord: WARNING: This causes a high risk for buffer underruns.
> 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.
You can use the realtime LSM (see list archives) to let specific groups
of users use mlockall and run RT tasks. Just load it like:
modprobe realtime gid=29
and make gid 29 your "cdrecord" group.
This should make CD burning as joeuser reliable as root. Most people
use this for low latency audio but I think cd burning is a wider and
completely unexplored application.
Lee
next prev parent reply other threads:[~2004-12-01 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 13:40 cd burning, capabilities and available modes J.A. Magallon
2004-12-01 16:36 ` Daniel Drake
2004-12-01 15:00 ` J.A. Magallon
2004-12-01 17:05 ` Lee Revell [this message]
2004-12-01 22:38 ` Bill Davidsen
2004-12-01 22:58 ` J.A. Magallon
2004-12-02 7:57 ` Frank Steiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1101920739.18170.29.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox