Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 09 Apr 2019 15:36:02 -0700
From:      Cy Schubert <Cy.Schubert@cschubert.com>
To:        freebsd-current@freebsd.org, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, David Boyd <David.Boyd49@twc.com>
Subject:   Re: lsof hangs with latest 13.0-CURRENT snapshot
Message-ID:  <3A0D37FF-317F-45CE-88E5-64E4642BACD6@cschubert.com>
In-Reply-To: <201904091941.x39JfY49061789@gndrsh.dnsmgr.net>
References:  <201904091941.x39JfY49061789@gndrsh.dnsmgr.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On April 9, 2019 12:41:34 PM PDT, "Rodney W=2E Grimes" <freebsd-rwg@gndrsh=
=2Ednsmgr=2Enet> wrote:
>> On Tue, 2019-04-09 at 12:20 -0700, Rodney W=2E Grimes wrote:
>> > > After upgrading from FreeBSD-13=2E0-CURRENT-amd64-20190328-r345620
>to
>> > > FreeBSD-13=2E0-CURRENT-amd64-20190404-r345863, lsof (4=2E92 from
>> > > packages)
>> > > hangs=2E
>> > >=20
>> > > This is true for bare metal installs and virtual machine
>installs=2E
>> > >=20
>> > > How to recreate:
>> > > =09
>> > > 	Install FreeBSD-13=2E0-CURRENT-amd64-20190404-r345863 snapshot=2E
>> > >=20
>> > > 	as root: lsof /sbin/init
>> > >=20
>> > > By running command with -b option, this error is displayed:
>> > >=20
>> > > lsof: status error on /sbin/init: Resource temporarily
>unavailable
>> > >=20
>> > > The return code is 1=2E
>> > >=20
>> > > This probably requires adjustment to lsof, but only the FreeBSD
>> > > snapshot changed, so I'll start here=2E
>> >=20
>> > Where did you get your lsof binary from?
>> >=20
>> > lsof has internal knowledge of kernel data structures=20
>> > and must be compiled to match the running system=2E
>> >=20
>> >=20
>> > > Thanks=2E
>> > > David Boyd=2E
>>=20
>>=20
>> lsof was installed via pkg install from pkg=2Efreebsd=2Eorg=2E
>
>That does not work well on ^head or for that mater any snapshot,
>as I said, lsof has internal knowledge of kernel data structures
>and must match the running kernel for it to work=2E
>
>It should be complaining about a version mismatch, but perhaps
>it was compiled recently enough that these are matching, but
>there is still a datastruct that changed=2E

Version mismatches are innocuous=2E I tend to use it on -current until it =
breaks, rebuilding it as needed=2E Rebuilding is a good time to update the =
port while I'm at it=2E This policy has served me well over the years=2E=20


--=20
Pardon the typos and autocorrect, small keyboard in use=2E
Cheers,
Cy Schubert <Cy=2ESchubert@cschubert=2Ecom>
FreeBSD UNIX: <cy@FreeBSD=2Eorg> Web: http://www=2EFreeBSD=2Eorg

	The need of the many outweighs the greed of the few=2E



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A0D37FF-317F-45CE-88E5-64E4642BACD6>