Hi James,
One option could be to eliminate the Apache logs. See the link below for details about this configuration:
https://www.mydigitallife.net/how-to-disable-and-turn-off-apache-httpd-access-and-error-log/If disabling the logs is not an option for you you can implement the logs rotation. The IBM Apache server delivers a program named rotetalogs for this purpose. See the link below:
http://publib.boulder.ibm.com/httpserv/manual70/programs/rotatelogs.htmlAfter you implemented the log rotation you can schedule an USS command in a batch job to delete logs with more than "n" days.
To delete files with more than 10 days you can issue this command:
find /caspool/websrv/logs/log* -mtime +10 -exec rm {} \;
The above command presumes you named the log files starting with log*.
For example:
Errorlog "|bin/rotatelogs logs/logerror.%Y-%m-%d-%H_%M_%S 86400"
CustomLog "|bin/rotatelogs logs/logaccess.%Y-%m-%d-%H_%M_%S 86400" common
The above statements in the httpd.conf file will rotate the logs at each 24 hours.
Regards,
Mario
------------------------------
Carlos Mario Silveira Filho
Principal Support Engineer
carlosmario.filho@broadcom.comBroadcom
------------------------------
Original Message:
Sent: 04-27-2020 10:57 AM
From: James Huckert
Subject: Spool Web server
Does anyone know if there is a way to automate or schedule a process to trim or clean up the access log and error logs for the spool web server component?
I ran out of space for one of the my spool web servers and it was because the access log and error logs were extremely large.
Any ideas would be appreciated
Thanks
James