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>
Split |
Close |
Expand all |
Collapse all |
--- old/usr/src/tools/scripts/bringovercheck.1onbld.man.txt
+++ new/usr/src/tools/scripts/bringovercheck.1onbld.man.txt
1 -bringovercheck(1ONBLD) illumos Build Tools bringovercheck(1ONBLD)
1 +BRINGOVERCHECK(1ONBLD) illumos Build Tools BRINGOVERCHECK(1ONBLD)
2 2
3 3
4 4
5 5 NAME
6 6 bringovercheck - Repair misordered workspace timestamps
7 7
8 8 SYNOPSIS
9 9 bringovercheck workspace
10 10
11 11 DESCRIPTION
12 12 Some versions of bringover(1ONBLD) fail to msync(2) writeable mappings;
13 13 this results in indeterminate modification times when the workspace
14 14 exists on certain filesystems. When this results in SCCS s. files
15 15 being newer than their respective checked-out source files, build
16 16 carnage may result (see sccscheck(1ONBLD) for one mitigating step being
17 17 taken).
18 18
19 19 If a workspace has been damaged by this bug, you can run bringovercheck
20 20 to detect and correct cases where a source file is older than its
21 21 corresponding SCCS s. file.
22 22
23 23 If no out-of-date files are found, bringovercheck will produce no
24 24 output; otherwise, it will produce a human-readable transcript which
25 25 includes filenames, last modification dates, and the output of the sccs
↓ open down ↓ |
14 lines elided |
↑ open up ↑ |
26 26 commands it uses to attempt to fix the problem.
27 27
28 28 Note that because the problem may involve deferred filesystem writes,
29 29 this script may not be fully effective if run immediately after a
30 30 bringover.
31 31
32 32
33 33
34 34
35 35
36 - 7 April 2006 bringovercheck(1ONBLD)
36 + April 7, 2006 BRINGOVERCHECK(1ONBLD)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX