On Mon, Mar 3, 2014 at 10:15 PM, enh wrote:
> On Sun, Mar 2, 2014 at 3:39 AM, Philippe Ombredanne
> wrote:
>> On Tue, Feb 25, 2014 at 8:49 PM, enh wrote:
[...]
>> On the pipes side, I am a bit more puzzled as what more could be done
>>
>> pipe(2) has nothing we could decode afaik?
>>
>> Are
On Sun, Mar 2, 2014 at 3:39 AM, Philippe Ombredanne
wrote:
> On Tue, Feb 25, 2014 at 8:49 PM, enh wrote:
>> actually, -y was my biggest wish-list feature :-)
>>
>> other things i've hated doing manually in the past include working out
>> exactly what a given socket is (usually "what's the remote
On Tue, Feb 25, 2014 at 8:49 PM, enh wrote:
> actually, -y was my biggest wish-list feature :-)
>
> other things i've hated doing manually in the past include working out
> exactly what a given socket is (usually "what's the remote address?").
> pipes too. in both cases the default /proc format is
