3 .\" The contents of this file are subject to the terms of the
   4 .\" Common Development and Distribution License (the "License").
   5 .\" You may not use this file except in compliance with the License.
   6 .\"
   7 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
   8 .\" or http://www.opensolaris.org/os/licensing.
   9 .\" See the License for the specific language governing permissions
  10 .\" and limitations under the License.
  11 .\"
  12 .\" When distributing Covered Code, include this CDDL HEADER in each
  13 .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  14 .\" If applicable, add the following below this CDDL HEADER, with the
  15 .\" fields enclosed by brackets "[]" replaced with your own identifying
  16 .\" information: Portions Copyright [yyyy] [name of copyright owner]
  17 .\"
  18 .\" CDDL HEADER END
  19 .\"
  20 .\" Copyright 2006 Sun Microsystems, Inc.  All rights reserved.
  21 .\" Use is subject to license terms.
  22 .\"
  23 .\" ident       "%Z%%M% %I%     %E% SMI"
  24 .\"
  25 .TH bringovercheck 1 "7 April 2006"
  26 .SH NAME
  27 .I bringovercheck
  28 \- Repair misordered workspace timestamps
  29 .SH SYNOPSIS
  30 .B bringovercheck
  31 workspace
  32 .SH DESCRIPTION
  33 Some versions of 
  34 .I bringover(1) 
  35 fail to 
  36 .I msync(2)
  37 writeable mappings; this results in indeterminate modification times
  38 when the workspace exists on certain filesystems.  When this results
  39 in SCCS s. files being newer than their respective checked-out source
  40 files, build carnage may result (see
  41 .I sccscheck(1)
  42 for one mitigating step being taken).
  43 
  44 If a workspace has been damaged by this bug, you can run
  45 bringovercheck to detect and correct cases where a source file is
  46 older than its corresponding SCCS s. file.
  47 
  48 If no out-of-date files are found, bringovercheck will produce no
  49 output; otherwise, it will produce a human-readable transcript
  50 which includes filenames, last modification dates, and the output of
  51 the sccs commands it uses to attempt to fix the problem.
  52 
  53 Note that because the problem may involve deferred filesystem writes,
  54 this script may not be fully effective if run immediately after a
  55 bringover.
  56 
  57 

   3 .\" The contents of this file are subject to the terms of the
   4 .\" Common Development and Distribution License (the "License").
   5 .\" You may not use this file except in compliance with the License.
   6 .\"
   7 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
   8 .\" or http://www.opensolaris.org/os/licensing.
   9 .\" See the License for the specific language governing permissions
  10 .\" and limitations under the License.
  11 .\"
  12 .\" When distributing Covered Code, include this CDDL HEADER in each
  13 .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  14 .\" If applicable, add the following below this CDDL HEADER, with the
  15 .\" fields enclosed by brackets "[]" replaced with your own identifying
  16 .\" information: Portions Copyright [yyyy] [name of copyright owner]
  17 .\"
  18 .\" CDDL HEADER END
  19 .\"
  20 .\" Copyright 2006 Sun Microsystems, Inc.  All rights reserved.
  21 .\" Use is subject to license terms.
  22 .\"
  23 .TH bringovercheck 1ONBLD "7 April 2006"


  24 .SH NAME
  25 .I bringovercheck
  26 \- Repair misordered workspace timestamps
  27 .SH SYNOPSIS
  28 .B bringovercheck
  29 workspace
  30 .SH DESCRIPTION
  31 Some versions of
  32 .I bringover(1ONBLD)
  33 fail to
  34 .I msync(2)
  35 writeable mappings; this results in indeterminate modification times
  36 when the workspace exists on certain filesystems.  When this results
  37 in SCCS s. files being newer than their respective checked-out source
  38 files, build carnage may result (see
  39 .I sccscheck(1ONBLD)
  40 for one mitigating step being taken).
  41 
  42 If a workspace has been damaged by this bug, you can run
  43 bringovercheck to detect and correct cases where a source file is
  44 older than its corresponding SCCS s. file.
  45 
  46 If no out-of-date files are found, bringovercheck will produce no
  47 output; otherwise, it will produce a human-readable transcript
  48 which includes filenames, last modification dates, and the output of
  49 the sccs commands it uses to attempt to fix the problem.
  50 
  51 Note that because the problem may involve deferred filesystem writes,
  52 this script may not be fully effective if run immediately after a
  53 bringover.
  54 
  55