Admin ServiceOptimizer Business as Usual Filestore HouseKeeping
- Paul Hindle
- Andrew Hill (Deactivated)
Admin ServiceOptimizer System Configuration Application Logfiles explains what logfiles are created, and where. As mentioned there, there is a need to regularly remove old log files, otherwise the filestore may become so full that new ones cannot be written. This section covers how this may be achieved in the various different o/s versions supported.
This can be done in Windows Explorer using the 'delete' function.
The recommendation is to use the standard UNIX 'find' command to find and then delete all files older than a certain number of days, e.g.
find $SPHOME/<instance> -type f -name '' -mtime +14 -exec rm -f {} \; -prune*
Here, the "*" character is used to mean all files older than 14 days.
Automated archive process
Ideally some form of automated archiving process should be configured so that there is no possibility of this requirement being forgotten.
UNIX Only
Note that SERVICEPower uses /tmp and you should ensure that there is sufficient space in it before starting the system (at least 160MB). If /tmp does not have sufficient space, the result is unpredictable but is likely to be prejudicial to the correct running of ServiceOptimizer.
In rare circumstances, a server process can crash, and a 'core' file is generated (for debugging). This can take up significant time and disk space. It is not recommended that the generation of the 'core' file be disabled (since this would make fault diagnosis very difficult), but if absolutely necessary this can be done for the current process as follows:
For the 'csh' shell:
limit coredumpsize 0
For the 'ksh' shell:
ulimit –c 0
See 'man csh' or 'man ksh' for more information.