Appendix B StorNext Administration Tasks
StorNext Log Rolling Administration
StorNext Log Rolling Administration
Changing Log Rolling Times
Use the following procedures to configure StorNext log rolling options.
Use this procedure to change the frequency of rolling the StorNext logs. This process requires that you edit the tldm crontab to set log times. Use this procedure to edit tdlm crontab.
1Log on as root.
2Edit the tdlm crontab and update the sn_log_update script. Below is an example crontab:
0 1,7,13,19 * * * /usr/adic/www/bin/cmdwrap /usr/adic/util/sn_log_update /usr/ adic
where 0 1,7,13,19 * * * designates the times when logs run.
| In this release of StorNext the sn_log_update information is overwritten | |
Log Rolling Options | ||
and no longer contains the $DEF_SIZE or the $DEF_LOGS variables. These | ||
| ||
| entries are now contained in the sn_log_update.cfg file | |
| You can change these options to optimize log rolling. | |
| • | |
| they are rolled. This directory is typically a managed directory. For | |
| example: | |
| sn_log_update | |
| where <dir> is the directory where you want the logs to reside. | |
| • $DEF_SIZE = 2000000: This is the default size at which logs are rolled. | |
| Edit this entry in the /usr/adic/util/sn_log_update.cfg file if you want | |
| the log sizes to be larger or smaller. | |
| • $DEF_LOGS = 28: This is the default number of logs that are saved | |
| before they are deleted. Edit this entry in the /usr/adic/util/ | |
| sn_log_update.cfg file if you want to save less than 28 logs or are | |
| saving the logs to a managed directory. |
StorNext 3.1.3 Installation Guide | 123 |
