Re: [Zope] Having to keep typing "./start &"
From: "Douglas Carnall" <dougie@carnall.org>
If I am right, then this is an FAQ. Each time I answer it, I plaintively wonder aloud why the -D flag would be the default, but I am generally ignored.
One reason is that without it, the server prints out nothing at all at startup, which is confusing to new users. To solve this two things need to be changed: 1. There need to be a possibility to set the error severity just like with stupid_log_file, even for printouts to stdoutput. Maybe the stupid_log_file could be made to be the standard way of logging, and it could log to stdout if no stupid_log_file was set? 2. The default level for stupid_log_file should be to print INFO and higher messages. Today the default is only to print PROBLEM and higher.
Lennart Regebro wrote:
From: "Douglas Carnall" <dougie@carnall.org>
If I am right, then this is an FAQ. Each time I answer it, I plaintively wonder aloud why the -D flag would be the default, but I am generally ignored.
One reason is that without it, the server prints out nothing at all at startup, which is confusing to new users. To solve this two things need to be changed:
1. There need to be a possibility to set the error severity just like with stupid_log_file, even for printouts to stdoutput. Maybe the stupid_log_file could be made to be the standard way of logging, and it could log to stdout if no stupid_log_file was set?
2. The default level for stupid_log_file should be to print INFO and higher messages. Today the default is only to print PROBLEM and higher.
Or, add a new "zope is started" message that is logged at a severity IMPORTANT_MESSAGE, which is at the same level as a PROBLEM. That should be very simple to implement. -- Steve Alexander
From: "Steve Alexander" <steve@cat-box.net>
Or, add a new "zope is started" message that is logged at a severity IMPORTANT_MESSAGE, which is at the same level as a PROBLEM.
The level could be somewhere inbetween INFO and PROBLEM, which would make more sense, I think. Still I'd rather see the level of that message as being set to INFO, and maybe the unimportant info messages changed to "BLATHER" because that level is made for unimportant messages as far as I can tell.
1. There need to be a possibility to set the error severity just like with stupid_log_file, even for printouts to stdoutput. Maybe the stupid_log_file could be made to be the standard way of logging, and it could log to stdout if no stupid_log_file was set?
STUPID_LOG_SEVERITY does this.
2. The default level for stupid_log_file should be to print INFO and
higher
messages. Today the default is only to print PROBLEM and higher.
No, the default is to log INFO (0) messages and higher. Here's a way to start Zope that outputs the STUPID_LOG_FILE to stdout: ./start -D STUPID_LOG_FILE= I use this all the time during development. Maybe it should be the standard, but then again, everybody wants something different ;-) - C
From: "Chris McDonough" <chrism@zope.com>
2. The default level for stupid_log_file should be to print INFO and higher messages. Today the default is only to print PROBLEM and higher.
No, the default is to log INFO (0) messages and higher.
Ah, OK. Yes, you are probably correct. The default when *not* using stupid log file is to not print INFO messages, however, which is what I wanted to say.
1. There need to be a possibility to set the error severity just like with stupid_log_file, even for printouts to stdoutput. Maybe the stupid_log_file could be made to be the standard way of logging, and it could log to stdout if no stupid_log_file was set?
STUPID_LOG_SEVERITY does this.
No, it doesn't. STUPID_LOG_SEVERITY only affects STUPID_LOG_FILE. However, I wasn't aware that you could set stupid_log_file to stdout, thanks for that info:
Here's a way to start Zope that outputs the stupid log file to stdout:
./start -D STUPID_LOG_FILE=
Since this is possible, I suggest that todays default output of messages get scrapped, and replaced by stupid_log_file, using stdoutput as default. This basically solves the problem. As an added neatness, I think some of the messages that today print out as INFO really should be set to BLATHER. :-) I just don't think this is particularily important information: ------ 2002-03-31T08:06:28 INFO(0) ZODB Opening database for mounting: '28351072_1017561254.820000' ------ 2002-03-31T08:06:28 INFO(0) ZODB Mounted database '28351072_1017561254.820000' at /temp_folder :-)
participants (3)
-
Chris McDonough -
Lennart Regebro -
Steve Alexander