Quote:Should I set cron to start at boot?IMO, yes. [by TrevorH]
I've installed Logwatch 7.3.6 via the rpm on my CentOS 5.4 server. The issue is I'm getting basically empty reports from logwatch. The only two sections which have any information are sam... [by edwaa]
My logwatch reports, within the CRON section, contain thousands of entries like those below.
Quote:TrevorH wrote:I'd start by googling "configure reverse dns" and go from there.Thank you. I will d... [by Mark4785]
So I'm getting this email from (I think) the Cron Daemon every 3ish hours:
> From: firstname.lastname@example.org (Cron Daemon)
> To: email@example.com
> Subject: Cron <root@localhost> /usr/share/clamav/freshclam-sleep
The default config for http-error logs in Logwatch on a CentOS 5 box (logwatch-7.4.0-1) includes the line:
That wipes out all lines, because Apache 2.2 uses StdDate format (e.g. Fri Sep 21 04:44:55 2012) not the standard Apache format (e.g. 04/Sep/2012:13:46:40 -0500).
during the upgrade process I was wondered for "replace init.d", and I said "keep", not replace. Now, apache2 is not working. I tried removing and upgrading again, but doesnt start.
I have this error message:
sudo /etc/init.d/cron start
Rather than invoking init scripts through /etc/init.d, use the service(8)
I tried to run logwatch at follows
[root@machine cron.daily]# ./0logwatch
ERROR: Date::Manip unable to determine TimeZone.
Execute the following command in a shell prompt:
The section titled TIMEZONES describes valid TimeZones
and where they can be defined.
My date is as follows
root@machine cron.daily]# date
Thu Aug 23 06:25:21 GMT 2012
Now based on details i
Quote:TrevorH wrote:Or add the CentOS disk to the Ubuntu grub menu.I'll work on that.regds.,Ramki. [by vrkrao]