> On Mon, Oct 22, 2012 at 1:27 PM, Frédéric Bastien <no...@nouiz.org> wrote:

>> Hi,

>> The easy hack would be to change sys.stdin to a file descriptop that
>> you open in writing.

>> Logger could be good, but that should be used only for what in inside
>> pylearn2. This don't fix the problem of the stuff the user print
>> itself.

>> jobman already redirect the stdout/stderr correctly to a file. You do
>> not need a database to use it. You can use "jobman cmdline" to just do
>> the rediction. "jobman cmdline --help" for detail. This will also add
>> some debug information that we gatter automatically, like the 'job
>> scheduler' job id, the host name, etc. I think it is better to collect
>> automatically some debug info in only one system if possible. We can
>> discuss where.

>> Can you tell me what you did finally?

> In this most recent case, I told the admins about some of the problems I was
> having,
> and they fixed something related to the "username server".

>> Also, on witch cluster you had the problem?

> briaree. Pretty much any time I have a problem on briaree, the logs never
> appear,
> or are missing a lot of output.

>> Fred

>> On Sun, Oct 21, 2012 at 2:02 PM, David Warde-Farley
>> <d.warde.far...@gmail.com> wrote:
>> > On Sun, Oct 21, 2012 at 1:54 PM, David Warde-Farley
>> > <d.warde.far...@gmail.com> wrote:
>> >> On Sun, Oct 21, 2012 at 10:48 AM, Ian Goodfellow
>> >> <goodfellow....@gmail.com> wrote:
>> >>> If the client is also using the logging module, would we overwrite
>> >>> their
>> >>> settings?
>> >>> I seem to remember there being a discussion of something like that
>> >>> happening
>> >>> on one of the theano mailing lists.

>> >> I think that can only happen if we modify the "global logger", which
>> >> we may want to but we needn't necessarily. I'll have a look at the
>> >> mailing list to see if I can find the issue.

>> > So here's the issue: the logging module has a concept of a "log
>> > level", so messages are classified in a severity ordering. INFO is
>> > higher priority than DEBUG, WARNING is higher than INFO, ERROR is
>> > higher than WARNING, and CRITICAL is higher than all. Then you tell
>> > the logger the minimum level you want to see.

>> > What had happened in Theano was that someone had modified the global
>> > logger state from minimum level NOTSET to minimum level DEBUG, so a
>> > bunch of third party modules also started spewing debug messages. This
>> > is pretty easily avoided.