David Vrensk wrote: > Yes, that would be preferrable. But all logrotate does is (1) rename > the log file and (2, optional) send a signal to the application to let > it know that the log file has been renamed, and hence, the application > should close its file handle and open a new one. Rails and Mongrel > don't answer to a signal with the semantics of (2) AFAIK.
The same code you execute upon deploy to bounce your application servers can be used to a similar effect, with no more user noticeable downtime (or risk) as simple deployment. Just have to configure logrotate with a custom post rotate hook. Zsombor -- Company - http://primalgrasp.com Thoughts - http://deezsombor.blogspot.com _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
