VDT Log Rotation

Several software packages included with the VDT create log files. Unless properly rotated these logs will continue to grow and eat up disk space. As of version 1.1.14, the VDT included tools to rotate these logs. Additionally, during a root install the user is given the option of having cron entries set up to rotate logs on a daily basis.

Globus Logs

The VDT uses Red Hat's logrotate tool to handle the following Globus log files:

• $VDT_LOCATION/globus/var/accounting.log
• $VDT_LOCATION/globus/var/globus-gatekeeper.log
• $VDT_LOCATION/globus/var/grid-info-system.log

The vdt-rotate-globus-logs command invokes logrotate with the config file at $VDT_LOCATION/vdt/etc/globus.logrotate. This is set up to rotate daily and save a week's worth of logs. See logrotate(8) if you want to learn more about Logrotate or use it to rotate other files.

GRAM Logs

GRAM stores one log file in a user's home directory for each job that they run. While each file isn't very large, there can be a lot of them. The script vdt-rotate-gram-logs can be used by a user to rotate their GRAM logs or by a system administrater to rotate GRAM logs for a number of users.

vdt-rotate-gram-logs attempts to determine which GRAM logs are completed, makes a tar archive of those logs and moves it to another location. The completed log files are then deleted from the user's home directory.

vdt-rotate-gram-logs --olddir ~/old-gram-logs

At many sites there are no "real" users who correspond to the UNIX accounts used by Globus submitters. In that case a system administrater can set up vdt-rotate-gram-logs to rotate logs for a number of pseudo-users.

vdt-rotate-gram-logs --olddir /var/old-gram-logs --user user1 --user user2