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

Split Close
Expand all
Collapse all
          --- old/usr/src/tools/scripts/bringovercheck.1
          +++ new/usr/src/tools/scripts/bringovercheck.1onbld
↓ open down ↓ 12 lines elided ↑ open up ↑
  13   13  .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  14   14  .\" If applicable, add the following below this CDDL HEADER, with the
  15   15  .\" fields enclosed by brackets "[]" replaced with your own identifying
  16   16  .\" information: Portions Copyright [yyyy] [name of copyright owner]
  17   17  .\"
  18   18  .\" CDDL HEADER END
  19   19  .\"
  20   20  .\" Copyright 2006 Sun Microsystems, Inc.  All rights reserved.
  21   21  .\" Use is subject to license terms.
  22   22  .\"
  23      -.\" ident       "%Z%%M% %I%     %E% SMI"
  24      -.\"
  25      -.TH bringovercheck 1 "7 April 2006"
       23 +.TH bringovercheck 1ONBLD "7 April 2006"
  26   24  .SH NAME
  27   25  .I bringovercheck
  28   26  \- Repair misordered workspace timestamps
  29   27  .SH SYNOPSIS
  30   28  .B bringovercheck
  31   29  workspace
  32   30  .SH DESCRIPTION
  33      -Some versions of 
  34      -.I bringover(1) 
  35      -fail to 
       31 +Some versions of
       32 +.I bringover(1ONBLD)
       33 +fail to
  36   34  .I msync(2)
  37   35  writeable mappings; this results in indeterminate modification times
  38   36  when the workspace exists on certain filesystems.  When this results
  39   37  in SCCS s. files being newer than their respective checked-out source
  40   38  files, build carnage may result (see
  41      -.I sccscheck(1)
       39 +.I sccscheck(1ONBLD)
  42   40  for one mitigating step being taken).
  43   41  
  44   42  If a workspace has been damaged by this bug, you can run
  45   43  bringovercheck to detect and correct cases where a source file is
  46   44  older than its corresponding SCCS s. file.
  47   45  
  48   46  If no out-of-date files are found, bringovercheck will produce no
  49   47  output; otherwise, it will produce a human-readable transcript
  50   48  which includes filenames, last modification dates, and the output of
  51   49  the sccs commands it uses to attempt to fix the problem.
  52   50  
  53   51  Note that because the problem may involve deferred filesystem writes,
  54   52  this script may not be fully effective if run immediately after a
  55   53  bringover.
  56   54  
  57   55  
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX