Forum: Rails deployment Mongrel process specific logging

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Bb4bdf2b184027bc38d4fb529770cde5?d=identicon&s=25 Wes Gamble (weyus)
on 2007-06-01 06:54
(Received via mailing list)

I have a client who has deployed an app. against 3 Mongrel processes.  I
have not been involved in the deployment at all, so if these question
are naive, I apologize in advance.

1) Are there Mongrel process-specific log files that are written to by
each Mongrel process?

2) I suspect the answer to #1 is no and that all of the Mongrel
processes just write to the same production.log file.  Is there a way to
identify which Mongrel process is servicing a given request recorded in

Ae6ea83481ed00bc4f83d766ea1500a3?d=identicon&s=25 Stoopidboi Stoopidboi (stoopidboi)
on 2007-06-04 02:36
Newbie here too, but maybe starting Mongrel with -l option might help to
redirect the log file. This page lists the start up options you can use

However I'm having a similar problem, but as my environment is Windows
the log option is not supported. Does anyone know of an alternative, or
can I obtain the listening port from Rails so that I can override
config.log_path with a derived filename?
This topic is locked and can not be replied to.