davood said:
Hello,
Could you please check the following URL,
http://www.webmasters-central.com/t/cron.shtml
http://www.uwsg.iu.edu/usail/automation/cron.html
It will help you
cPanel or Apache error_logs?
Both can be handled by logrotate which needs some fine tuning to work properly.
http://www.webhostgear.com/144.html
Both can be handled by logrotate which needs some fine tuning to work properly.
http://www.webhostgear.com/144.html
k. One last try.
The cron command that logrotate uses is: /usr/sbin/logrotate /etc/logrotate.conf. Of course this presumes a logrotate.conf file which is referenced in the previous link.
Other possible may be to use something like cat /dev/null > {filename}
The cron command that logrotate uses is: /usr/sbin/logrotate /etc/logrotate.conf. Of course this presumes a logrotate.conf file which is referenced in the previous link.
Other possible may be to use something like cat /dev/null > {filename}
The link that sawbuck gave to you details all you need to do to have your logs rotated. There's an application that runs on your server called logrotate exactly for that function which already runs in cron every day or week, depending on your server setup. Adding an additional crontab to run it separately won't make much difference for that reason and is probably a bad idea as it defeats the object of running logrotate in the first place.
thanks.. but for some reason mine does not rotate until there have been 500 errors... and all that happends is on the 501st it simply pushes the oldest one out...chirpy said:
what i am trying to do is completely clean it out after about 100 errors.
Thanks.
davood, you are getting hung-up on syntax, for what you want to do.
Cron jobs / logrotate all work on "time" and not "amount". As you can setup to run a specific logrotate -- a Cron job itself -- on a "daily" basis, it wouldn't matter how many errors there are.
Cron jobs / logrotate all work on "time" and not "amount". As you can setup to run a specific logrotate -- a Cron job itself -- on a "daily" basis, it wouldn't matter how many errors there are.
So if it is currently be cleared (rotated) by a daily cron job then simply move the logrotate cron to /etc/cron.hourly and execute it that way.
davood,
For emptying a file, you can do "cp /dev/null /path/to/file".
So for instance if your error_log is in the public_html folder, you can have this in your cron for instance,
I would recommend however that you fix whatever is causing all those 501s first.
Hope this helps.
For emptying a file, you can do "cp /dev/null /path/to/file".
So for instance if your error_log is in the public_html folder, you can have this in your cron for instance,
This will automatically empty your error_log file every day at 1 o'clock.
I would recommend however that you fix whatever is causing all those 501s first.
Hope this helps.
You need to do a bit more than copying null into it. You also have to restart apache afterwards as the original file and its space allocation will remoain until you do so on disk.
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
| B | Error: You must specify a subdomain. | Domain Management | 1 | |
|
raw error logs for domains. | Domain Management | 4 | |
| D | error logs for cron | Domain Management | 2 | |
| W | /scripts/runlogsnow cron error | Domain Management | 14 | |
| W | 2 domains + logs + errors | Domain Management | 0 |