Forum: Ruby on Rails where is WEBrick (daemon mode) output? not in log/server.log

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Dan T. (Guest)
on 2005-12-29 01:22
I am running WEBrick in daemon mode (with the -d option). Where is the
server output that would ordinarily be on my console if I ran without
the -d option?
APP_ROOT/log/server.log is empty and not being appended to, though it is
owned by the same user WEBrick is running as and has write permissions.

The only files in APP_ROOT/log are:
development.log
production.log
server.log
test.log

Where else could the output be?
Thanks in advance......
David R. (Guest)
on 2005-12-29 02:43
(Received via mailing list)
If you're starting WEBrick with $RAILS_ROOT/script/server, it looks
like the answer is /dev/null. If you're using WEBrick.new() directly,
you should be able to pass in the log_file as the first parameter.

Take a look at the code in your Ruby installation (mine is at /usr/
local/lib/ruby/1.8/), under the webrick/ directory. webrick/server.rb
has code to redirect STDIN, STDOUT, and STDERR to /dev/null when
running in daemon mode. Also, webrick/log.rb defaults to a log_file
of nil if one is not specified in the WEBrick::Log.new() call, which
causes log output to go to STDERR. I don't see a way to pass in an
option to specify the logfile when starting with script/server.

Anyone else have a line on this? This seems like too basic a thing to
not be able to do.

David
David R. (Guest)
on 2005-12-29 02:49
(Received via mailing list)
This should read "...WEBrick::Log.new()...". Again, I don't see a way
to pass a specific log file through from the command line.
This topic is locked and can not be replied to.