6205 onbld manuals should be declared as 1onbld
Reviewed by: Dan McDonald <danmcd@omniti.com>
Reviewed by: Josef Sipek <jeffpc@josefsipek.net>

*** 1,6 ****
! wsdiff(1)                        User Commands                       wsdiff(1)
  
  
  
  wsdiff - report differences between proto area objects
  
--- 1,6 ----
! wsdiff(1ONBLD)                illumos Build Tools               wsdiff(1ONBLD)
  
  
  
  wsdiff - report differences between proto area objects
  
*** 138,157 ****
         usr/lib/mdb/kvm/sparcv9/genunix.so
  
         user@example$ cat results
         <... verbose differences only for genunix.so ...>
  
!        Example 4: Invoking wsdiff through nightly(1)
  
!        By specifying -w in NIGHTLY_OPTIONS, nightly(1) will use wsdiff(1) to
!        determine which objects look different, compared to the previous build.
!        A pre-existing proto area must exist for wsdiff(1) to compare against.
!        nightly(1) will move aside the pre-existing proto area (renaming it to
!        $ROOT.prev under proto), and will invoke wsdiff at the end of the
!        build. The list of changed objects will be reported in the nightly mail
!        message, and a results file "wsdiff_results" will appear in the nightly
!        log area.
  
         Example 5: Influencing the level of paralelism
  
         wsdiff spawns a number of threads by default after it determines the
         list of files for comparison. Default number of threads is based on the
--- 138,157 ----
         usr/lib/mdb/kvm/sparcv9/genunix.so
  
         user@example$ cat results
         <... verbose differences only for genunix.so ...>
  
!        Example 4: Invoking wsdiff through nightly(1ONBLD)
  
!        By specifying -w in NIGHTLY_OPTIONS, nightly(1ONBLD) will use
!        wsdiff(1ONBLD) to determine which objects look different, compared to
!        the previous build. A pre-existing proto area must exist for
!        wsdiff(1ONBLD) to compare against. nightly(1ONBLD) will move aside the
!        pre-existing proto area (renaming it to $ROOT.prev under proto), and
!        will invoke wsdiff at the end of the build. The list of changed objects
!        will be reported in the nightly mail message, and a results file
!        "wsdiff_results" will appear in the nightly log area.
  
         Example 5: Influencing the level of paralelism
  
         wsdiff spawns a number of threads by default after it determines the
         list of files for comparison. Default number of threads is based on the
*** 159,172 ****
         threads for processing to some other value the DMAKE_MAX_JOBS
         environment variable can be used:
  
         $ DMAKE_MAX_JOBS=24 wsdiff proto_base proto_patch
  
!        Note that this variable is also used for nightly(1) so when run from
!        nightly(1), wsdiff will honor the setting.
  
  SEE ALSO
!        lintdump(1), nightly(1), elfdump(1),
  
  
  
!                                   15 Jul 2010                        wsdiff(1)
--- 159,172 ----
         threads for processing to some other value the DMAKE_MAX_JOBS
         environment variable can be used:
  
         $ DMAKE_MAX_JOBS=24 wsdiff proto_base proto_patch
  
!        Note that this variable is also used for nightly(1ONBLD) so when run
!        from nightly(1ONBLD), wsdiff will honor the setting.
  
  SEE ALSO
!        nightly(1ONBLD), elfdump(1),
  
  
  
!                                   15 Jul 2010                   wsdiff(1ONBLD)