[galaxy-dev] Log rotation tips

I set up logrotate on our production galaxy instance here, but after moving the file Galaxy (or more likely paste I imagine) doesn't re-open the log file. Is there some post-rotate action I can set in my logrotate command to let galaxy know that I pulled the logging rug out from under it? On apache this would be a SIGHUP, but some daemons use SIGUSRs of various flavors. How are others handling logs that grow without bounds? -- Ry4an Brase 612-626-6575 Software Developer Application Development University of Minnesota Supercomputing Institute http://www.msi.umn.edu