OTOH Rails 3.2 does have a major logging improvement, tagged logging, which by default shows process IDs. It would be useful to have a filter script that runs t

OTOH Rails 3.2 does have a major logging improvement, tagged logging, which by default shows process IDs. It would be useful to have a filter script that runs through the log and detangles requests based on process IDs. I have the same issue with daemons, even prior to 3.2. Tagged logging helps to solve the problem for those too, as it's easy to output an environment variable that's set by the starting script.