Bugzilla – Bug 2129
Gridftp logging levels (is 7>10?)
Last modified: 2004-10-25 10:13:49
You need to
before you can comment on or make changes to this bug.
In the docs for 3.9.2, it says that the debug level (for -d) is between 1 and
7, and in CVS it says:
debug_level Log level. 1 only logs errors, 16 logs everything
When trying to debug an earlier gridftp problem, setting the debug level to 10
gave me less information than with a debug level of 7 (248 vs. 3146 bytes).
Debug level 16 gave me 0 bytes.
That should read 15. (It is just a bitmask). This got me thinking about user
specified log levels. I can interperet the user log level as what they give ||
every level below, i.e. your 16 would have become a 31 internally, but then
users lose the ability to selectively pick different levels. Obviously giving
them that ability means I have to provide tags for the levels and the user will
specify a list of tags. i.e. -l error,info,dump ... (numbers could still be
used of course) Is any of this useful? Would a user ever want a high level
output but not the lower levels?
I think a straight scale of 0 (only errors) to 15 (everything) is easy to use
and makes sense. The ORing of levels would only be useful if logical names
were used, not numbers (ie, error,info,dump instead of 7,8,12).
Note that with logical names we would get very close to syslog(3).
Subject: RE: Gridftp logging levels (is 7>10?)
Yes, I definitely think so. If you had zeroed in on the area where the
problem was, you would only want that info, not wade through tons of other
I made log levels selectable with text tags (error,warn,info,dump,all), or a
single digit. If the digit is given it will make sure to select all levels
below and including that digit. This should handle the common case of a user
picking an arbitrary high number expecting to get a lot of output. People that
want selective levels will use the tags.