Mongrel users - Dec 2006 - no log/mongrel.log file on win32, looking for suggestions...

Hello Mongrels around the world!

Been thinking a way to unify the issue I described in the subject.

For those who aren''t aware, mongrel (actually, mongrel_rails) only
generate the log file if daemonize was used (-d)

That means no log file under windows, due his lack of
fork/daemonization capabilities.

Now, users that need to run mongrel on windows cannot report and fill
the empty spaces with information truly important about why mongrel
isn''t playing nice (or being a bad dog?).

I will like some suggestions on this area, which I think is important,
looking to reduce platform specific *notes*.

A. Should mongrel on windows redirect the output (log information)
from console to a log file, only if -d daemonize was specified (in a
similar way like *nix platforms).

or

B. Or redirect always and suppress all the console information (STDOUT
and STDERR).

Please, mongrel users on windows affected by this provide feedback.

Thanks in advance your time.

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

On Tue, 26 Dec 2006 22:38:45 -0300
"Luis Lavena" <luislavena at gmail.com> wrote:
> Hello Mongrels around the world!
Insult! :-)

<snip>
> A. Should mongrel on windows redirect the output (log information)
> from console to a log file, only if -d daemonize was specified (in a
> similar way like *nix platforms).
I don''t think this is good since -d means daemonize.  If people run it
from the command line with -d and it just shows no output then they''ll
get confused.
> or
> B. Or redirect always and suppress all the console information (STDOUT
> and STDERR).
Is it possible that the service can just redirect STDERR and STDOUT to the log
file?  That''d fall more in line with how daemonize works on Unix.
 
> Please, mongrel users on windows affected by this provide feedback.

-- 
Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu
http://www.zedshaw.com/
http://www.awprofessional.com/title/0321483502 -- The Mongrel Book
http://mongrel.rubyforge.org/
http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.

On 12/27/06, Zed A. Shaw <zedshaw at zedshaw.com>
wrote:
> On Tue, 26 Dec 2006 22:38:45 -0300
> "Luis Lavena" <luislavena at gmail.com> wrote:
>
> > Hello Mongrels around the world!
>
> Insult! :-)
>
Ok, ok, now you''re king hope you don''t send troops to execute
me :-P
> <snip>
> > A. Should mongrel on windows redirect the output (log information)
> > from console to a log file, only if -d daemonize was specified (in a
> > similar way like *nix platforms).
>
> I don''t think this is good since -d means daemonize.  If people
run it from the command line with -d and it just shows no output then
they''ll get confused.
>
> > or
>
> > B. Or redirect always and suppress all the console information (STDOUT
> > and STDERR).
>
> Is it possible that the service can just redirect STDERR and STDOUT to the
log file?  That''d fall more in line with how daemonize works on Unix.
>
That is possible, but will force users to run in service mode even if
they are just debugging (like I do, open a terminal and run
mongrel_rails there).

Also, will require mongrel_service be more clever and actually parse
the config script or command line for references to log file...
something that I don''t plan to include in the following weeks (busy
with other stuff).
> Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu
BTW, where is my MUDCRAP-CE cert? I voted for you!... ;-)

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi