Bug 150697 - genkernel man page doesn't match behavior
Bug#: 150697 Product:  Gentoo Hosted Projects Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: genkernel@gentoo.org Reported By: ulmer@ulmer.org
Component: genkernel
URL: 
Summary: genkernel man page doesn't match behavior
Keywords:  
Status Whiteboard: 
Opened: 2006-10-09 19:02 0000
Description:   Opened: 2006-10-09 19:02 0000
The genkernel manual page states:

       --debuglevel=<0-5>
              This  controls  the out verbosity level of genkernel output - if
              this is set to 0, minimal debugging is done; if this is set to 5
              as much output as possible is given.

       --debugfile=<outfile>
              This  outputs full debugging data; regardless of --debuglevel to
              the file <outfile>. By default this is /var/log/genkernel.log.


It is not the case that --debugfile causes full debuging output regardless of
verbosity level, there is a significant difference in output with and without a
--debuglevel.

I'm attaching two --debugfile(s) generate with these commands:

# genkernel --lvm2 --kernel-config=/tmp/myconfig --debugfile=/tmp/genkernel.out
all

# genkernel --lvm2 --kernel-config=/tmp/myconfig
--debugfile=/tmp/genkernel-debug5.out --debuglevel=5 all

It doesn't matter which way this is resolved, but the man page, them embedded
documentation, and the behavior ought to be consistent.

------- Comment #1 From Stephen Ulmer 2006-10-09 19:04:26 0000 -------
Created an attachment (id=99248) [details]
debugfile with default debugging level (supposedly 1, from config file)

------- Comment #2 From Stephen Ulmer 2006-10-09 19:05:36 0000 -------
Created an attachment (id=99249) [details]
debugfile with debug level specified as 5

------- Comment #3 From Chris Gianelloni (RETIRED) 2007-06-21 20:16:43 0000 -------
This is in SVN now with the patch from bug #180161

------- Comment #4 From Chris Gianelloni (RETIRED) 2007-08-22 19:54:05 0000 -------
Please test genkernel 3.4.9_prer1 or better.  This should be fixed now.