Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
linux:grsec [2006/12/16 00:48] a |
linux:grsec [2008/09/26 20:23] a |
||
|---|---|---|---|
| Line 204: | Line 204: | ||
| gradm -D | gradm -D | ||
| + | |||
| ==== grsec iptables patch ==== | ==== grsec iptables patch ==== | ||
| FIXME TODO | FIXME TODO | ||
| + | |||
| + | ===== Tips / troubleshooting ===== | ||
| + | |||
| + | ==== complaints of grsecurity-kernel about RLIMIT_CORE being 0 ==== | ||
| + | |||
| + | If, while running program x, a segmentation fault occurs in program x and syslog outputs the following string: | ||
| + | Apr 17 11:55:06 yyy kernel: grsec: attempted resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 by (x:z) UID(y) EUID(y), parent (y:y) UID(y) EUID(y) | ||
| + | then kernel tried to write a core-file for the program x to disk, BUT the max size of the core file is set to 0. | ||
| + | Growing the maximum size of a core file: | ||
| + | |||
| + | # ulimit -S -c 8192 | ||
| + | |||
