On Nov 13, 2007 5:07 PM, Rob Banz <rob@xxxxxxxxxxx> wrote: > > > On Nov 13, 2007, at 16:47, Gerard wrote: > > > I am running squatter at 3am as a cron job on all of my servers. Over > > the passed week I have one server where squatter spikes the load and > > ends up locking up the server at around 8am every morning. Yeah, it > > seems to take that long to run which may be an issue in itself. Has > > anyone come accross this or have a suggestion on how to get squatter > > to perform better? > > ---- > > What OS? > > Squatter shouldn't be causing "load spikes" unless there's some > resource contention for lock files, etc. > > You should also make sure that if you're running cyr_expire, you're > NOT running it concurrently with squatter. Bad things happen.* To > get around this, I created a "nightly" shell script which runs > cyr_expire, then squatter, and kick that off as a scheduled task in my > cyrus.conf. > > * The bad things come into play if expire & squatter are processing > the same mailbox at the same time. Squatter will probably just > "stop", and not tell you why. > > -rob > ---- > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > It seems like the default for cyr_expire runs at 4:00AM (delprune cmd="cyr_expire -E 3" at=0400) and I start squatter at 3:00AM. Do you think that this would cause the spike and server to lock up? We are running RHEL4U4 ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
