Wilson,
The decision on what messages to save is somewhat subjective. Many questions should be asked while deciding to turn saved messages on or off. Can you easily resend from the source system? Can you selectively resend from source system. Is it a one to one or a one to many interface configuration? Many times it is advantageous to save an inbound message for troubleshooting reasons. We can always track down the exact message that was sent to us whenever we have questions about a interface message. We also use the inbound saved message file to verify a message was received and at what time. If you had code that deleted (killed) certain messages, you may have difficulty proving the message was ever received by cloverleaf since it would not be available on your outbound saved message file.
What you could do is cycle and compress your saved message files on a nightly basis. A simple script would look like this:
setroot
setsite invision
hcicmd -p process_adt -c ‘. output_cycle’
hcicmd -p process_adt -c ‘adt_thread_in save_cycle in’
hcicmd -p process_adt -c ‘adt_thread_out save_cycle out’
find $HCISITEDIR/exec/processes -name *.old.idx -exec compress -f {} ;
find $HCISITEDIR/exec/processes -name *.old.msg -exec compress -f {} ;
The above sample cycles the logfiles, cycles the saved message files, compresses the .old saved message file. Hope this helps.
.
.