Incorrect Process.setrlimit spec on (some?) Linux
Reported by Wilson Bilkovich | March 1st, 2008 @ 02:24 PM | in 0.11
The Process.setrlimit spec for RLIMIT_MEMLOCK needs revision on Linux.
It appears to fail because the lim/max return values are not necessarily valid arguments to setrlimit.
While this is retarded, it is real, and needs some work.
I am currently installing Ubuntu so that I can debug this mess.
Process.setrlimit and Process.getrlimit limit and get total size for mlock(2) (bytes) ERROR
Invalid argument:
Errno.handle at kernel/core/errno.rb:19
Process.setrlimit at kernel/core/process.rb:35
Object#__script__ {} at ./spec/ruby/1.8/core/process/setrlimit_spec.rb:73
Comments and changes to this ticket
-
Wilson Bilkovich March 1st, 2008 @ 02:37 PM
- → Milestone changed from “1.0” to “1.0 preview”
- → State changed from “new” to “open”
-
Wilson Bilkovich June 25th, 2008 @ 09:55 AM
- → Tag changed from “” to “compatibility spec ubuntu”
- → Milestone changed from “1.0 preview” to “0.10”
-
Wilson Bilkovich July 10th, 2008 @ 03:38 PM
- → Milestone changed from “0.10” to “0.11”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
