Re: [PATCH v3] Added Support for Optionally Specifying Resource Limits

2011-03-15 Thread Daniel Wagner
Good Morning Grant, > > On 03/14/2011 06:42 PM, Grant Erickson wrote: > >> > >> [ ... ] > >> > >> AC_ARG_WITH(dbusconfdir, AC_HELP_STRING([--with-dbusconfdir=PATH], > >> [path to D-Bus config directory]), [path_dbusconf=${withval}], > > > > This D-Bus change looks a bit odd. Is this a left ove

Re: [PATCH v3] Added Support for Optionally Specifying Resource Limits

2011-03-14 Thread Grant Erickson
On 3/14/11 3:25 PM, Daniel Wagner wrote: > I think I overlooked few things again. Sorry about that. > > BTW, The subject title should not be too long (IIRC 52 chars max). > And some prefix would also be nice, e.g. > > "rlimit: Add resource limit support" > > or something like that. I'm not a nat

Re: [PATCH v3] Added Support for Optionally Specifying Resource Limits

2011-03-14 Thread Daniel Wagner
Hi Grant, I think I overlooked few things again. Sorry about that. BTW, The subject title should not be too long (IIRC 52 chars max). And some prefix would also be nice, e.g. "rlimit: Add resource limit support" or something like that. I'm not a native english speaker. You might have a better

[PATCH v3] Added Support for Optionally Specifying Resource Limits

2011-03-14 Thread Grant Erickson
Added support for optionally specifying, via a global, read-only configuration file, system resource limits for address space, core files, data segment size, file size, lockable memory, open files, number of processes and stack size. This mirrors in function, almost identically, resource limit han