Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Nov 2017 14:46:58 +0000
From:      Karl Pielorz <kpielorz_lst@tdx.co.uk>
To:        "Kevin P. Neal" <kpn@neutralgood.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Security updates / 'procstat' to find daemons to restart - reliable?
Message-ID:  <675C99D459C8A5345CBCDFE3@[10.12.30.106]>
In-Reply-To: <20171130142120.GA71392@neutralgood.org>
References:  <45CAA442C95AA5B35EF0AF7C@[10.12.30.106]> <20171130142120.GA71392@neutralgood.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help


--On 30 November 2017 09:21 -0500 "Kevin P. Neal" <kpn@neutralgood.org> 
wrote:

> Unverified guess:

Hmm, seems a pretty good guess :)

> When the library is updated the old library is deleted first. But since
> the library is still open it still exists. It just doesn't show up in any
> directory. That's normal Unix behavior.
>
> Now, the guess is that if the library doesn't show up in any directory
> then procstat can't figure out the name of the library. Is there any
> mention of a library that has no name?

That would certainly explain the behaviour, and running a 'before' and 
'after' procstat - I can see:

Before 'freebsd-update install'
 1093  ... r-x  460 507 31 10 CN-- vn /lib/libcrypto.so.7

After,
 1093  ... r-x  460 512 31 10 CN-- vn


So that appears to be the case, the file has 'changed' (i.e. inode etc.) - 
and is no longer available to be displayed.

I can't see any obvious "marker" (other than a blank filename) for this - 
so I guess I have to run the check before the 'install' - note what's using 
what, run the install - then restart the affected software.

Thanks for the guess! (I mean reply! :)

Regards,

-Karl



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?675C99D459C8A5345CBCDFE3>