This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients gvanrossum, neologix, r.david.murray, vstinner, yselivanov
Date 2014-07-02.06:50:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1BGCJNDZizu-0HvZ1HC54yo_T37sDhs0F9hGvkP0v+cA@mail.gmail.com>
In-reply-to <1404260454.1.0.374930516525.issue21901@psf.upfronthosting.co.za>
Content
There's probably a special mechanism due to vserver which makes the
kernel kill the process instead of failing with EPERM, but it's really
surprising.

What happens if you try the following:
$ python -c "from resource import *; _, hard =
getrlimit(RLIMIT_NOFILE); setrlimit(RLIMIT_NOFILE, (hard, hard))"

You could run the process under strace to see what's going on: you'll
likely just see the reception of a signal though. Maybe "dmesg" would
show interesting logs.
History
Date User Action Args
2014-07-02 06:50:57neologixsetrecipients: + neologix, gvanrossum, vstinner, r.david.murray, yselivanov
2014-07-02 06:50:57neologixlinkissue21901 messages
2014-07-02 06:50:56neologixcreate