On Sat, May 03, 2014 at 11:08:36PM -0400, Oleg Drokin wrote:
> Hello!
>
> On May 3, 2014, at 10:33 PM, Greg Kroah-Hartman wrote:
> >> I don't think I saw complaints about proc files, the complaints I saw were
> >> mostly about
> >> reading env variables directly and the like so that was the focus
Hello!
On May 3, 2014, at 10:33 PM, Greg Kroah-Hartman wrote:
>> I don't think I saw complaints about proc files, the complaints I saw were
>> mostly about
>> reading env variables directly and the like so that was the focus of this
>> patch.
>> Did I miss some side discussion? Any pointers?
> N
On Sat, May 03, 2014 at 09:20:06PM -0400, Oleg Drokin wrote:
>
> On May 3, 2014, at 7:29 PM, Greg Kroah-Hartman wrote:
>
> > On Sun, Apr 27, 2014 at 10:21:52PM -0400, Oleg Drokin wrote:
> >> Insted of meddling directly in process environment variables
> >> (which is also not possible on certain p
On May 3, 2014, at 7:29 PM, Greg Kroah-Hartman wrote:
> On Sun, Apr 27, 2014 at 10:21:52PM -0400, Oleg Drokin wrote:
>> Insted of meddling directly in process environment variables
>> (which is also not possible on certain platforms due to not exported
>> symbols), create jobid_name proc file to
On Sun, Apr 27, 2014 at 10:21:52PM -0400, Oleg Drokin wrote:
> Insted of meddling directly in process environment variables
> (which is also not possible on certain platforms due to not exported
> symbols), create jobid_name proc file to represent this info
> (to be filled by job scheduler epilogue
Insted of meddling directly in process environment variables
(which is also not possible on certain platforms due to not exported
symbols), create jobid_name proc file to represent this info
(to be filled by job scheduler epilogue).
Signed-off-by: Oleg Drokin
CC: Andreas Dilger
---
.../staging/
