From: Jan Klod <janklodvan@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] resource overstep RLIMIT_CORE
Date: Wed, 21 Jan 2009 10:16:47 +0000 [thread overview]
Message-ID: <200901211016.47819.janklodvan@gmail.com> (raw)
In-Reply-To: <1232466326.7039.7.camel@localhost>
On Tuesday 20 January 2009 15:45:25 Ned Ludd wrote:
> On Tue, 2009-01-20 at 11:17 +0000, Jan Klod wrote:
> > On Tuesday 20 January 2009 10:49:24 Manuel Leithner wrote:
> > > On Tue, 20 Jan 2009 11:40:33 +0100, Jan Klod wrote:
> > > > Hi list,
> > > >
> > > > could someone explain the meaning and possible causes (if possible)
> > > > of this message: "denied resource overstep by requesting 4096 for
> > > > RLIMIT_CORE against limit 0?
> > >
> > > One of your processes crashed and tried to dump its core, but since the
> > > RLIMIT_CORE is set to 0 (i. e. no core dumps are to be created), it
> > > can't do so.
> >
> > Ah, so it is just a secondary problem. Its ssmtp crashing. First it makes
> > a segfault, then receives signal 11 by grsec, then overstep.
>
> A segfault is signal 11. It's not two events but one. And grsec is not
> sending the signal in anyway but rather just logging that it happened.
>
> > Anyone here using
> > it with grsec?
>
> Lots of people.
Ok, my advice is: don't use some of characters \#,\$,\,, maybe \( in password
for ssmtp...
prev parent reply other threads:[~2009-01-21 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 10:40 [gentoo-hardened] resource overstep RLIMIT_CORE Jan Klod
2009-01-20 10:49 ` Manuel Leithner
2009-01-20 11:17 ` Jan Klod
2009-01-20 15:45 ` Ned Ludd
2009-01-20 19:25 ` Jan Klod
2009-01-21 0:30 ` Magnus Granberg
2009-01-21 10:16 ` Jan Klod [this message]
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=200901211016.47819.janklodvan@gmail.com \
--to=janklodvan@gmail.com \
--cc=gentoo-hardened@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