Hi, 2012/1/7 Julien Valroff <[email protected]>: > Can you please send the related part of rkhunter.log?
This does not appear on any rkhunter log file. If I think more about this, it cannot be in the log file if this goes to stderr and to the output of cron -> email. > I cannot reproduce this on my system. Does it happen after you have closed > your X session (ie. gnome-keyring could still be running) or also after a > fresh boot? The strange part is that the message comes from other cron.daily jobs too, not only from rkhunter. For example in the last days: # Date: Thu, 05 Jan 2012 20:26:29 +0200 /etc/cron.daily/apt: WARNING: gnome-keyring:: no socket to connect to # Date: Fri, 06 Jan 2012 07:02:53 +0200 # Date: Sat, 07 Jan 2012 13:09:49 +0200 /etc/cron.daily/00logwatch: WARNING: gnome-keyring:: no socket to connect to # Date: Sun, 08 Jan 2012 13:20:10 +0200 /etc/cron.daily/00logwatch: WARNING: gnome-keyring:: no socket to connect to /etc/cron.daily/apt: WARNING: gnome-keyring:: no socket to connect to # Date: Mon, 09 Jan 2012 10:12:19 +0200 /etc/cron.daily/apt: WARNING: gnome-keyring:: no socket to connect to So, on Jan 08 it appeared on two jobs (00logwatch and apt). I'm undecided to which package to reassign: cron or gnome-keyring? What do you think? Thanks _______________________________________________ forensics-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel
