> Hello, > > Okay, in which case I would suspect that the PATH used when run via cron > is different from when used interactively. As such if you ran 'rkhunter > --propupd' interactively, then some files may well be reported as > present or missing from the system. > > If you are using 'sudo', then maybe using 'sudo su -' will give you the > same PATH as used by cron.
After a bit more testing, it's definitely cron-related, though no less strange. I'm using 2 wrapper scripts, one to run the check, and another to update the file properties database. Both are using the full path to the rkhunter binary. If I run the update script from the command line, running the check from the command-line (whether through the wrapper script or directly) works as expected. Running the check through cron generates the "file does not exist on the system" error. If I run the update script through cron, running the check through cron works as expected, but running it from the command-line (wrapper script or not) gives the aforementioned error. Interestingly enough, running the scripts through "at now" displayed the same behaviour as the command-line, and not the cron jobs. Ah, well, there goes my idea of doing the propupd through at. -- Daniel ------------------------------------------------------------------------------ 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-d2dcopy1 _______________________________________________ Rkhunter-users mailing list Rkhunter-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkhunter-users
