Re: Purge msg misunderstanding

Marc Chapados wrote:
> We installed Messaging Server 6 (2005Q4) and we don't understand 
> exactly how work the purge (/opt/SUNWmsgsr/lib/purge -num=5).

This "purge" command is not about the automatic removal of messages from the 
store.  This purge command removes old log files.

The "imexpire" command is what you are looking for.


> We keep the default configuration like following:
> local.sched.enable = 1
> local.schedule.expire = "0 23 * * * /opt/SUNWmsgsr/sbin/imexpire"
> local.schedule.msprobe = "5,15,25,35,45,55 * * * 
> * /opt/SUNWmsgsr/lib/msprobe"
> local.schedule.purge = "0 0,4,8,12,16,20 * * 
> * /opt/SUNWmsgsr/lib/purge -num=5"
> local.schedule.return_job = "30 0 * * * /opt/SUNWmsgsr/lib/return_job"
>
> We configured some expire rules (in the 
> file /opt/SUNWmsgsr/config/store.expirerule) and these expire rules 
> work perfectly each day at 23:00.
>  
> After the messagers are expired, we wonder which command will purge 
> (remove permanently) these messagers from the disk (1.msg, 2.msg, ...)?

Tt is actually the same imexpire command that does it.  But it happens in a 
two-stage process.  The .msg files cannot be removed immediately.  So there is a 
configutil option to control how many hours must have passed since a message was 
deleted and expunged before the .msg file can be removed.  You should see your 
expire rules expunge a message one day and remove the .msg file the next day.

Kelly


> What is exactly the purge functionality (/opt/SUNWmsgsr/lib/purge -
> num=5)? We know that -num=5 means that expired after 5 versions but 
> what does it mean exactly?
>  
> When we lunch the purge binary without any parameter 
> (/opt/SUNWmsgsr/lib/purge) no message is purged. Why?
>  
> Does this purge command log anywhere in a log file?
>  
> Thanks for your help!