Date: Thu, 21 Jun 2001 17:32:51 +0100 From: Ceri <ceri@techsupport.co.uk> To: Trevin Chow <trevin@mail.com> Cc: 'James Housley' <jim@thehousleys.net>, questions@freebsd.org Subject: Re: logging of /usr/libexec/atrun Message-ID: <20010621173251.A14974@cartman.techsupport.co.uk> In-Reply-To: <BCCBC5E8BA377141B125D2C5F91ABA5B02A69E47@red-msg-07.redmond.corp.microsoft.com>; from trevin@mail.com on Thu, Jun 21, 2001 at 09:28:04AM -0700 References: <3B321EE1.8BC71E1D@thehousleys.net> <BCCBC5E8BA377141B125D2C5F91ABA5B02A69E47@red-msg-07.redmond.corp.microsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 21, 2001 at 09:28:04AM -0700, Trevin Chow said: > > >Instead just filter out the atrun lines. > >grep -v atrun /var/log/cron | more > > This doesn't work too well since the cron logs are getting archived in > cron.0.gz, cron.1.gz, etc after a certain size I'm guessing? So I have > to unzip each of the cron logs to find what I want... or is there a > better way? gzip -dc cron.[0-9].gz | grep -v atrun /var/log/cron | more ? Ceri -- I probably wouldn't like you. Really. I really probably wouldn't like you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010621173251.A14974>