Index

Subject : Re: LUG: Anything wrong with this cron entry?

From : Kevin Hunter <hunteke@earlham.[redacted]>

Date : Fri, 07 Oct 2011 16:09:52 -0400

Parent


At 3:11pm -0400 Fri, 07 Oct 2011, Daniel Underwood wrote:
> No, didn't check syslog. Tried to check it now, but its history
> doesn't extend to the first of this month.

Hmm ... Do you not have older log files? On most systems I
administrate, logrotate maintains a list of older logs files, up to some
specified number of days. For instance, on my desktop machine for which
I don't really need log files for very long, it only stores the most
recent week:

$ ll syslog*
-rw-r----- 1 syslog adm 34K 2011-10-07 16:04 syslog
-rw-r----- 1 syslog adm 167K 2011-10-07 10:34 syslog.1
-rw-r----- 1 syslog adm 50K 2011-10-06 19:48 syslog.2.gz
-rw-r----- 1 syslog adm 93K 2011-10-05 10:38 syslog.3.gz
-rw-r----- 1 syslog adm 42K 2011-10-03 00:40 syslog.4.gz
-rw-r----- 1 syslog adm 23K 2011-10-02 00:47 syslog.5.gz
-rw-r----- 1 syslog adm 42K 2011-10-01 02:57 syslog.6.gz
-rw-r----- 1 syslog adm 45K 2011-09-30 12:08 syslog.7.gz

Meaning that you should be able to see as far back as your logrotate is
configured to store logs. Now, if cron isn't even running, or otherwise
isn't logging, that's a different story ...

Cheers,

Kevin


Replies :