John:
> > OK, I see in the conf file this line:
> > INSTALLDIR=/usr/local
> > If this means that it wants rkhunter to be there, this could be the
> > problem.
> >
> No, that is fine.
>
> > I don't see a PATH indicated in the log file:
> >
> This is the line:
>
> > [03:05:03] Info: Using '/sbin /bin /usr/sbin /usr/bin' as the command
> > directories
In rkhunter.conf the following line appears to specify where RKHunter expects
the executables to be:BINDIR="/bin /usr/bin /sbin /usr/sbin"
So, I would think that modifying this to:BINDIR="/bin /usr/bin /sbin /usr/sbin
/usr/local/bin"should solve this problem.
> As can be seen it is not looking /usr/local/bin and so won't find
> the /usr/local/bin/rkhunter command.
>
> You need to either:
> 1) Run 'rkhunter --propupd' with the PATH the same as above,
> 2) or modify your root PATH to include /usr/local/bin.
By "root PATH" do you mean the OS PATH or that specified in the conf file as
above? It looks like /usr/local/bin is already in the OS system path:
echo
$PATH/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin
Ralph
> >
> >
> >
> >
> > John.
> >
> >
> > --
> > John Horne Tel: +44 (0)1752 587287
> > Plymouth University, UK Fax: +44 (0)1752 587001
>
> --
> John Horne Tel: +44 (0)1752 587287
> Plymouth University, UK Fax: +44 (0)1752 587001
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Rkhunter-users mailing list
Rkhunter-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rkhunter-users
