This is a discussion on slibclean command usage within the AIX Operating System forums, part of the Unix Operating Systems category; --> Hi At what circumstances, slibclean should be used ? Suppose, I remove a shared library file which is still ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi At what circumstances, slibclean should be used ? Suppose, I remove a shared library file which is still loaded on global text segment with the "rm" command and put a new shared library in. Will program start always reference to the newly loaded shared library in the shared text segment ? I think installp always rm old files if it is not an update fileset. Thanks. |
| ||||
| Lo, Michael [CAR:VR30:EXCH] wrote: > Hi > > At what circumstances, slibclean should be used ? When you need to get the system to stop using a module for some reason. And the module is no longer in use by any process. > Suppose, I remove a shared library file which is still loaded on global > text segment with the "rm" command and put a new shared library in. No problem. > Will program start always reference to the newly loaded shared library > in the shared text segment? Yes. If the module is in use and you "rm" it, then you remove the filesystem entry, not the file. The file will get fully removed once it is no longer in use by the shared lib segment. In the meantime, creating a new file causes a new inode to be used, and the loader detects this and loads the new copy. (It keeps track by filesystem/ inode, which is always unique.) -- Gary R. Hook / AIX PartnerWorld for Developers / These opinions are MINE __________________________________________________ ______________________ |
| Thread Tools | |
| Display Modes | |
|
|