Date: Wed, 2 Jul 2014 20:01:20 +0700 From: Victor Sudakov <vas@mpeks.tomsk.su> To: Maciej Suszko <maciej@suszko.eu> Cc: Anton Sayetsky <vsjcfm@gmail.com>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: /usr/local/lib/compat/pkg/ cleanup ? Message-ID: <20140702130119.GA78768@admin.sibptus.tomsk.ru> In-Reply-To: <20140702084125.50882034@helium> References: <20140627161801.GA38362@admin.sibptus.tomsk.ru> <CAFG2KC%2BgC7igexqnOqgGz0s=AzMacZg=3mobvGZv97KABKOong@mail.gmail.com> <20140627165322.GA40497@admin.sibptus.tomsk.ru> <CAFG2KCLBnhXEx3B6rP6ir2hRiVvhRLiA7Lx5e_YJV2E2E2%2B1wQ@mail.gmail.com> <20140628135325.GA55592@admin.sibptus.tomsk.ru> <20140702084125.50882034@helium>
next in thread | previous in thread | raw e-mail | index | archive | help
Maciej Suszko wrote: > > > With "rm -rf /usr/local/lib/compat/pkg" you don't need all those > > sophisticated tools you mentioned above. A missing library will > > quickly make itself known :) and then you can forcible reinstall the > > affected packages. > > Unless you do it remotely, using openssh from ports which might be > affected... then you have a problem :) > > I usually do it like that: > > 1) find /usr/local -type f -print0 | xargs -0 ldd > /tmp/ldds > 2 ) search the ldds file for "not found" or "compat" > 3) find what packages affected files belongs to > 4) recompile affected packages Thank you, Maciej. This method is kinda harsh, but at least it does not require additional software written in ruby etc etc. I just moved /usr/local/lib/compat/pkg/* away, did the ldd check, found nothing suspicious or missing, and removed all those libraries altogether. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140702130119.GA78768>