On Fri, Aug 23, 2019 at 07:33:29PM +0200, Martijn van Duren wrote:
> On 8/23/19 7:06 PM, Gilles Chehade wrote:
> > On Fri, Aug 23, 2019 at 09:03:51AM +0200, Martijn van Duren wrote:
> >> Hello,
> >>
> >
> > Hello,
> >
> >
> >> When running processes with proc-exec any logging send over stderr is
On 8/23/19 7:06 PM, Gilles Chehade wrote:
> On Fri, Aug 23, 2019 at 09:03:51AM +0200, Martijn van Duren wrote:
>> Hello,
>>
>
> Hello,
>
>
>> When running processes with proc-exec any logging send over stderr is
>> not very intelligible since the process name is automatically generated
>> and
On Fri, Aug 23, 2019 at 09:03:51AM +0200, Martijn van Duren wrote:
> Hello,
>
Hello,
> When running processes with proc-exec any logging send over stderr is
> not very intelligible since the process name is automatically generated
> and results in , which make them hard to read.
>
Agreed
Hello,
When running processes with proc-exec any logging send over stderr is
not very intelligible since the process name is automatically generated
and results in , which make them hard to read.
To clean this up I reckon we can do three things:
1) Add an extra optional proc parameter that sets