1 |
On Tuesday 20 January 2009 15:45:25 Ned Ludd wrote: |
2 |
> On Tue, 2009-01-20 at 11:17 +0000, Jan Klod wrote: |
3 |
> > On Tuesday 20 January 2009 10:49:24 Manuel Leithner wrote: |
4 |
> > > On Tue, 20 Jan 2009 11:40:33 +0100, Jan Klod wrote: |
5 |
> > > > Hi list, |
6 |
> > > > |
7 |
> > > > could someone explain the meaning and possible causes (if possible) |
8 |
> > > > of this message: "denied resource overstep by requesting 4096 for |
9 |
> > > > RLIMIT_CORE against limit 0? |
10 |
> > > |
11 |
> > > One of your processes crashed and tried to dump its core, but since the |
12 |
> > > RLIMIT_CORE is set to 0 (i. e. no core dumps are to be created), it |
13 |
> > > can't do so. |
14 |
> > |
15 |
> > Ah, so it is just a secondary problem. Its ssmtp crashing. First it makes |
16 |
> > a segfault, then receives signal 11 by grsec, then overstep. |
17 |
> |
18 |
> A segfault is signal 11. It's not two events but one. And grsec is not |
19 |
> sending the signal in anyway but rather just logging that it happened. |
20 |
> |
21 |
> > Anyone here using |
22 |
> > it with grsec? |
23 |
> |
24 |
> Lots of people. |
25 |
|
26 |
Ok, my advice is: don't use some of characters \#,\$,\,, maybe \( in password |
27 |
for ssmtp... |