Print this page
6282 ONBLD man pages not pbchk clean
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Reviewed by: Josef Sipek <jeffpc@josefsipek.net>
   1 wsdiff(1ONBLD)                illumos Build Tools               wsdiff(1ONBLD)
   2 
   3 
   4 
   5 wsdiff - report differences between proto area objects
   6 
   7 SYNOPSIS
   8        wsdiff [-dvVst] [-r results] [-i filelist] old new
   9 
  10 DESCRIPTION
  11        The wsdiff utility detects and reports on object differences found
  12        between two proto areas constructed from the same workspace. This can
  13        be useful when trying to understand which objects have changed as a
  14        result of a particular source change.
  15 
  16        old specifies the baseline proto area constructed without the source
  17        change. new specifies the proto area constructed with the source
  18        change. Both old and new should be constructed from the same workspace,
  19        otherwise wsdiff will find object differences not associated with the
  20        source change.
  21 


 152        "wsdiff_results" will appear in the nightly log area.
 153 
 154        Example 5: Influencing the level of paralelism
 155 
 156        wsdiff spawns a number of threads by default after it determines the
 157        list of files for comparison. Default number of threads is based on the
 158        number of on-line CPUs present in the system. To set the number of
 159        threads for processing to some other value the DMAKE_MAX_JOBS
 160        environment variable can be used:
 161 
 162        $ DMAKE_MAX_JOBS=24 wsdiff proto_base proto_patch
 163 
 164        Note that this variable is also used for nightly(1ONBLD) so when run
 165        from nightly(1ONBLD), wsdiff will honor the setting.
 166 
 167 SEE ALSO
 168        nightly(1ONBLD), elfdump(1),
 169 
 170 
 171 
 172                                   15 Jul 2010                   wsdiff(1ONBLD)
   1 WSDIFF(1ONBLD)                illumos Build Tools               WSDIFF(1ONBLD)
   2 
   3 
   4 
   5 wsdiff - report differences between proto area objects
   6 
   7 SYNOPSIS
   8        wsdiff [-dvVst] [-r results] [-i filelist] old new
   9 
  10 DESCRIPTION
  11        The wsdiff utility detects and reports on object differences found
  12        between two proto areas constructed from the same workspace. This can
  13        be useful when trying to understand which objects have changed as a
  14        result of a particular source change.
  15 
  16        old specifies the baseline proto area constructed without the source
  17        change. new specifies the proto area constructed with the source
  18        change. Both old and new should be constructed from the same workspace,
  19        otherwise wsdiff will find object differences not associated with the
  20        source change.
  21 


 152        "wsdiff_results" will appear in the nightly log area.
 153 
 154        Example 5: Influencing the level of paralelism
 155 
 156        wsdiff spawns a number of threads by default after it determines the
 157        list of files for comparison. Default number of threads is based on the
 158        number of on-line CPUs present in the system. To set the number of
 159        threads for processing to some other value the DMAKE_MAX_JOBS
 160        environment variable can be used:
 161 
 162        $ DMAKE_MAX_JOBS=24 wsdiff proto_base proto_patch
 163 
 164        Note that this variable is also used for nightly(1ONBLD) so when run
 165        from nightly(1ONBLD), wsdiff will honor the setting.
 166 
 167 SEE ALSO
 168        nightly(1ONBLD), elfdump(1),
 169 
 170 
 171 
 172                                  July 15, 2010                  WSDIFF(1ONBLD)