[tahoe-lafs-trac-stream] [tahoe-lafs] #1421: increase_rlimits() tries to set RLIMIT_CORE high, which grsec disallows

[tahoe-lafs]

#1421: increase_rlimits() tries to set RLIMIT_CORE high, which grsec disallows
-------------------------+---------------------------
 Reporter:  zooko        |          Owner:  somebody
     Type:  enhancement  |         Status:  new
 Priority:  minor        |      Milestone:  undecided
Component:  code         |        Version:  1.8.2
 Keywords:  grsecurity   |  Launchpad Bug:
-------------------------+---------------------------
 Originally reported in #982 by ioerror:

  Grsec disallows a resource overstep when tahoe requests 4196256 for
 {{{RLIMIT_CORE}}}. To get tahoe started, you'll need to add the following
 to the init.d script:

  {{{
  ulimit -c 4196256
  }}}

 But, when I read
 [source:trunk/src/allmydata/util/iputil.py?annotate=blame&rev=4971#L12 the
 source code of increase_rlimits()] I don't see any evidence that we
 deliberately set {{{RLIMIT_CORE}}}. (We certainly never intended to.)

 So, is it that calling {{{resource.getrlimit(resource.RLIMIT_NOFILE)}}} is
 also setting {{{RLIMIT_CORE}}}? Perhaps this is a bug in the Python
 standard library. Could someone with grsecurity installed please reproduce
 this issue and show the complete error message?

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1421>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage