Linux, FreeBSD, Juniper, Cisco / Network security articles and troubleshooting guides

FAQ
It is currently Wed Jul 15, 2020 1:11 pm


Username:
Subject:
Message body:
Enter your message here, it may contain no more than 60000 characters. 

Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
Font size:
 
Font colour
Options:
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Disable BBCode
Disable smilies
Do not automatically parse URLs
Confirmation code
Confirmation code:
In an effort to prevent automatic submissions, we require that you enter both of the words displayed into the text field underneath.
     

Topic review - ldconfig - possibly dangerous: How to fix FreeBSD lib paths after running 'ldconfig' \w arguments
Author Message
Post subject: ldconfig - possibly dangerous: How to fix FreeBSD lib paths after running 'ldconfig' \w arguments  |  Post Posted: Fri Apr 26, 2013 7:42 pm
After running the "ldconfig" command on freeBSD, it will clear library paths used by binaries, so system will be unusable.


Code:
[root@system]# ldconfig   
[root@system]# vim
Shared object "libiconv.so.3" not found, required by "vim"
[root@system]# man man
Shared object "gcc46/libstdc++.so.6" not found, required by "tbl"
Shared object "gcc46/libstdc++.so.6" not found, required by "groff"



The fix is to start the 'ldconfig' rc script:
Code:
[root@system]# /etc/rc.d/ldconfig start
Jump to:  
News News Site map Site map SitemapIndex SitemapIndex RSS Feed RSS Feed Channel list Channel list


Delete all board cookies | The team | All times are UTC - 5 hours [ DST ]



phpBB SEO