$ docker run --rm dcm4che/rm-wildfly-logs -h
Provide cron service for daily deletion of WildFly Server log files
Usage: docker run -v /host/log-dir1:/log-dir1 -v /host/log-dir2:/log-dir2
-d dcm4che/rm-wildfly-logs /log-dir1 /log-dir2
with
'-v /host/log-dir1:/log-dir1 -v /host/log-dir2:/log-dir2'
to bind mount WildFly Server directories on the docker host containing server
log files into the container. The directory path(s) inside the container must
match with the passed argument(s):
'/log-dir1 /log-dir2'.
The number of days after which log files are deleted can be configured by
Environment Variables:
WILDFLY_SERVER_LOG_RETENTION_DAYS - number of days after which 'server.log*'
files in specified directories are deleted, 7 days by default.
WILDFLY_AUDIT_LOG_RETENTION_DAYS - number of days after which 'audit-log.log*'
files in specified directories are deleted, 7 days by default.
The cron service may also be used for daily deletion of logged HL7 messages of
dcm4chee archive instances by bind mount logged HL7 messages into the container
and passing the directory path(s) inside the container by Environment Variable:
ARC_HL7_LOG_DIRS - space separated directory paths of logged HL7 messages of
dcm4chee archive instances
ARC_HL7_LOG_RETENTION_DAYS - number of days after which '*.hl7' files in
directories specified by ARC_HL7_LOG_DIRS are deleted, 7 days by default.
Excutable scripts bind mounted into the container under '/init.d' will be
executed in lexical sort order at each container startup and may be used to
configure cron to run (additionally) other tasks periodically.
E.g.:
$ docker run -v /host/init.d:/init.d -v /host/used-blocks:/used-blocks
-d dcm4che/rm-wildfly-logs
with executable
$ cat /host/init.d/get-used-blocks
#!/bin/sh
if [ ! -f $0.done ]; then
crontab -l \
| sed "$ i */1\t*\t*\t*\t*\tquota -w | sed -n '\/fs1/p' | cut -f2 -d ' ' > /used-blocks/fs1" \
| crontab -
touch $0.done
fi
will query the number of used blocks of a filesystem every minute and
write it to a file.
Related #3709 #4584