Debian Bug Tracking System wrote:
helo=treasure.calvinsplayground.de)This is an automatic notification regarding your Bug report #299566: gringotts: fails to start unless run with strace, which was filed against the gringotts package.
It has been closed by one of the developers, namely Bastian Kleineidam <[EMAIL PROTECTED]>.
Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact the developer, by replying to this email.
Debian bug tracking system administrator (administrator, Debian Bugs database)
Received: (at 299566-done) by bugs.debian.org; 15 Mar 2005 09:06:55 +0000
>From [EMAIL PROTECTED] Tue Mar 15 01:06:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mx01.qsc.de [213.148.129.14]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DB80s-0004vB-00; Tue, 15 Mar 2005 01:06:54 -0800
Received: from port-212-202-192-37.dynamic.qsc.de ([212.202.192.37]
by mx01.qsc.de with smtp (Exim 3.35 #1) id 1DB80M-0008Mo-00 for [EMAIL PROTECTED]; Tue, 15 Mar 2005 10:06:22 +0100 Received: (qmail 30423 invoked by uid 1000); 15 Mar 2005 09:06:22 -0000 Date: Tue, 15 Mar 2005 10:06:22 +0100 From: Bastian Kleineidam <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Bug#299566: gringotts: fails to start unless run with strace Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <[EMAIL PROTECTED]> X-GPG-Fingerprint: A977 46CD F709 4611 A44D 27FA 781C 2504 32EC 6F3E X-GPG-Key: 32EC6F3E Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-4.4 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER, UPPERCASE_25_50 autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level:
Hi David,
you have to increase the memlock limit for users, please read /usr/share/doc/gringotts/README.Debian for more info. If you have a suggestion on how to make this information more easy to find, please let me know it.
Regards, Bastian
Hi Bastian,
My bad -- this is clearly explained. It's still so esoteric that it would be useful to
get a bit more of an explanation. For instance, the limit is set to 50000 -- but 50000 what?
And the * in the README -- I take it they should be included?
When I issue ulimit -l, I get "unlimited" for user root and 32 for regular users. How
and when does the new value get activated? Must Pam be restarted? Does I need to log out and back in?
My gringotts now works whether I make the change recommended or not. If I comment it out again,
gringotts still works without complaints. It looks to me like something else solved the problem, but
how do I know?
My general impression is that this is completely mysterious, and since I have no idea what I'm doing,
I'm tempted to suggest it become part of the preconfiguration of gringotts.
Since things are working, I suggest closing the bugreport. Out of usability considerations, I suggest
we find a way to spare the common user this mystifying and in my case inconclusive procedure.
In the meantime, gringotts is working great. But by changing this limit value and activating it in
ssh, gdm, su, and login, did I just strengthen or weaken my security? What are the potential costs down
the line for making the change? Perhaps I didn't need to increase the limit, but did need to enable
pam_limits.so? If so, what are the potential consequences of doing this?
In brief, the instructions may work (I can't tell), but most users would have no idea what they're doing.
Best, Dave
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
