> On Mar 05, 2015, at 12.51, Wietse Venema wrote:
>
> btb:
>> when reviewing postscreen entries in logs, it's difficult to quickly
>> grep for entries relevant to a particular session, since the only unique
>> value in the entry is the pid, which is quite long lived and spans many
>> sessions
On 3/5/2015 11:36 AM, btb wrote:
> when reviewing postscreen entries in logs, it's difficult to quickly
> grep for entries relevant to a particular session, since the only
> unique value in the entry is the pid, which is quite long lived and
> spans many sessions. i wondered how practical it might
btb:
> when reviewing postscreen entries in logs, it's difficult to quickly
> grep for entries relevant to a particular session, since the only unique
> value in the entry is the pid, which is quite long lived and spans many
> sessions. i wondered how practical it might be to include a unique i
when reviewing postscreen entries in logs, it's difficult to quickly
grep for entries relevant to a particular session, since the only unique
value in the entry is the pid, which is quite long lived and spans many
sessions. i wondered how practical it might be to include a unique id
along with
