Thanks George. That worked just fine. My current nessusd is in /usr/local/sbin, but I also found nessusd in /usr/sbin. /usr/sbin is in the PATH of the root, but not /usr/local/sbin, so the old instance was called� The interesting questions then are: -Why did my two installations end up in two different locations (I didn�t specify a prefix), -Why did not uninstall-nessus remove the older nessusd in /usr/sbin (I ran it before I even started ./configure for the new installation)? (Rhetorical questions I guess, unless someone would like to discuss this area further).
Thanks again:-D -Terje ----- Original Message ----- From: George Theall <[EMAIL PROTECTED]> Date: Thu, 25 Sep 2003 12:10:40 -0400 To: [EMAIL PROTECTED] Subject: Re: libnessus.so.1 missing > On Thu, Sep 25, 2003 at 10:48:44AM -0500, Terje Tollisen wrote: > > > I installed nessus by hand both times. I unpacked the tarballs in > > /home/terje/nessusdownload, and did the ./configure, make, make install > > from the directories created. I used no precompiled packages and no > > packet manager. > > > > I didn�t specify a prefix. How/why do I specify this? > > You'd do it like "./configure --prefix=/usr" when you first run > configure for each component. > > > /usr/local/lib contains �libnasl.so -> libnasl.so.2.0.7� and > > �libnasl.so.2�, and other files (listed at the end of my post) but not > > �libnasl.so.1� It might be somewhere else, but I haven�t found it. > > > I�ll look through my log from the installation for any errors. > > (I can only find config.log files, but I sent all output from the > > ./configure, make, make install to a text file. Are there any actual > > logfiles of the entire installation?) > > No, there aren't. But as long as you redirected stdout and stderr from > the commands you should be able to see any errors. > > > itds1:/usr/local/sbin # ldd nessusd > > libnasl.so.2 => /usr/local/lib/libnasl.so.2 (0x40038000) > > libnessus.so.2 => /usr/local/lib/libnessus.so.2 (0x40060000) > > This tells you that nessusd needs to load libnessus.so.2 and will use > the copy located in /usr/local/lib. This is good. > > I wonder if the problem is that you have another instance of nessusd in > your path, one that relies on libnessus.so.1. What happens if you do > "which nessusd"? Does it report "/usr/local/sbin/nessusd"? If so, what > happens if you run "/usr/local/sbin/nessusd -d"? If not, the version it > finds is probably the source of your problems; rename it so it isn't > used and try things again. > > > George > -- > [EMAIL PROTECTED] -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers
