From: Mrugesh Karnik <mrugeshkarnik@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] No working "burning" cdrom
Date: Thu, 9 Nov 2006 13:30:36 +0530 [thread overview]
Message-ID: <200611091330.41622.mrugeshkarnik@gmail.com> (raw)
In-Reply-To: <200611090828.11974.mailing-gentoo@sailorferris.com>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On Thursday 09 November 2006 12:57, Luigi Pinna wrote:
> Alle 06:49, giovedì 9 novembre 2006, Mrugesh Karnik ha scritto:
> >[...]
> > Its to do with a kernel upgrade. Do a ulimit -l unlimited before
> > starting k3b in the same session.
>
> As user:
> $ ulimit -l unlimited
> bash: ulimit: max locked memory: cannot modify limit: Operation not
> allowed
>
> as root it is works!
> Now the question is how can I rescue it as default and allow it to
> users?
> What does it mean a kernel update?
> Thanks, Luigi
Yes, it works as root. I was just investigating ways to set that only
for growisofs. One way is to set it in /etc/profile, but that'll affect
all processes. I'll let you know when I find the solution. One solution
I can think of is to run ulimit followed by growisofs in a subshell..
but the issue is with being root. I'll let you know.
As for the kernel upgrade, this limit was imposed in 2.6.16 or something
from what I read.
--
----------------------------------------
Mrugesh Karnik
GPG Key 0xBA6F1DA8
Public key on http://wwwkeys.pgp.net
----------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-09 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 23:14 [gentoo-user] No working "burning" cdrom Luigi Pinna
2006-11-09 1:04 ` Neil Bothwick
2006-11-09 5:49 ` Mrugesh Karnik
2006-11-09 7:27 ` Luigi Pinna
2006-11-09 8:00 ` Mrugesh Karnik [this message]
2006-11-09 9:40 ` Neil Bothwick
2006-11-09 10:01 ` Mrugesh Karnik
2006-11-09 10:16 ` Neil Bothwick
2006-11-09 22:30 ` Luigi Pinna
2006-11-10 0:39 ` b.n.
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=200611091330.41622.mrugeshkarnik@gmail.com \
--to=mrugeshkarnik@gmail.com \
--cc=gentoo-user@lists.gentoo.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