Il 1 dicembre 2016 14:04:30 CET, Jeremie Courreges-Anglas ha
scritto:
>Jiri B writes:
>
>>> lsof is a problem. It is tightly coupled to the base system, enough
>to
>>> require /usr/src/sys checked out to be able to build it. This means
>>> that it breaks quite frequently:
>>
>> Correcting Pa
Jiri B writes:
>> lsof is a problem. It is tightly coupled to the base system, enough to
>> require /usr/src/sys checked out to be able to build it. This means
>> that it breaks quite frequently:
>
> Correcting Pascal's mail...
>
> IMO lsof is used because BSD' netstat
> doesn't show PID of a p
On Thu, Dec 01, 2016 at 07:49:22AM -0500, Jiri B wrote:
> > lsof is a problem. It is tightly coupled to the base system, enough to
> > require /usr/src/sys checked out to be able to build it. This means
> > that it breaks quite frequently:
>
> Correcting Pascal's mail...
LOL, .co != .com :) Stu
> lsof is a problem. It is tightly coupled to the base system, enough to
> require /usr/src/sys checked out to be able to build it. This means
> that it breaks quite frequently:
Correcting Pascal's mail... IMO lsof is used because BSD' netstat
doesn't show PID of a process with open sockets. fst
lsof is a problem. It is tightly coupled to the base system, enough to
require /usr/src/sys checked out to be able to build it. This means
that it breaks quite frequently:
http://marc.info/?l=openbsd-ports&s=lsof
It also needs /dev/mem access and doesn't even work without sysctl
kern.allowkm
