[lkml]   [2009]   [Oct]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/3] extend get/setrlimit to support setting rlimits external to a process (v7)
On Mon, Oct 19, 2009 at 08:52:15PM -0400, Neil Horman wrote:
> Ok, I give. I was hoping that some of the requestors of this feature would pipe
> up and support the use case for the proc file interface to set limits. clearly
> they're not that interested, but I still think theres merit in the patch. So
> heres version 7 of this patch set. Its the same as before, but the proc
> interface has been dropped, leaving only the syscall interface behind. I've
> tested the interface on intel 32 and 64 bit, with success
> Summary:
> Its been requested often that we have the ability to read and modify process
> rlimit values from contexts external to the owning process. Ideally this allows
> sysadmins to adjust rlimits on long running processes wihout the need to stop
> and restart those processes, which incurs undesireable downtime. This patch
> enables that functionality, It does so in two places. First it enables process
> limit setting by writing to the /proc/pid/limits file a string in the format:
> <limit> <current limit> <max limit> > /proc/<pid>/limits
> where limit is one of
> [as,core,cpu,data,fsize,locks,memlock,msgqueue,nice,nofile,nproc,rss,rtprio,rttime]
> Secondly it allows for programatic setting of these limits via 2 new syscalls,
> getprlimit, and setprlimit, which act in an identical fashion to getrlimit and
> setrlimit respectively, except that they except a process id as an extra
> argument, to specify the process id of the rlimit values that you wish to
> read/write
> Signed-off-by: Neil Horman <>

Ping? Any thoughts

 \ /
  Last update: 2009-10-28 15:47    [W:0.142 / U:10.540 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site