Red Hat Bugzilla – Bug 439428
'updated libraries' test needs better verbiage
Last modified: 2014-03-16 23:13:17 EDT
Description of problem:
Lots of warnings of the form:
Warning(01) Process init (pid: 1) is using shared object
that was probably updated!
This should probably be more clearly stated that in many cases, this is
*normal*, if you've updated recently.
Version-Release number of selected component (if applicable):
I think that "was probably updated" is enough or what do you mean with more
clearly? If we say in this messages that this is in most cases "normal" then
users will ignore this messages - this whole test :] If you have updated ld.so
then it is better to reboot the system, if you have updated libs that are used
by apache for example, then you should restart apache...
Possibly a description of how/why you'd see this.
If you want to really dig deep, it's possible to see if/when it was updated by
trawling the rpm database or yum log. Would be messy code, though.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Description field was improved for this purpose.
$ sudo sectool --info removedlibs
Name : removedlibs
Script name : removedlibs.sh
Groups : filesystem
Levels : 3 4 5
Description : Checks if libraries mapped into memory are the same as the
libraries on the disk.
To get rid of this warnings simply restart these processes (their names and PIDs
are in messages printed out by this test). Use the command service(8) to restart
processes that belong to a running system service.
sectool-0.8.0-1.fc9 has been submitted as an update for Fedora 9
sectool-0.8.0-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.