|
|
1.1 root 1: .TH NCHECK 8 "4 February 1983"
2: .UC 4
3: .SH NAME
4: ncheck \- generate names from i-numbers
5: .SH SYNOPSIS
6: .B /etc/ncheck
7: [
8: .B \-i
9: numbers ] [
10: .B \-a
11: ] [
12: .B \-s
13: ] filesystem
14: .SH DESCRIPTION
15: .B N.B.:
16: For most normal file system maintenance, the function of
17: .I ncheck
18: is subsumed by
19: .IR fsck (8).
20: .PP
21: .I Ncheck
22: with no argument
23: generates a pathname vs. i-number
24: list of all files
25: on a set of default file systems.
26: Names of directory files are followed by `/\fB.\fR'.
27: The
28: .B \-i
29: option reduces the report to only those files whose i-numbers follow.
30: The
31: .B \-a
32: option
33: allows printing of the names
34: .RB ` . '
35: and
36: .RB ` .. ',
37: which are ordinarily suppressed.
38: The
39: .B \-s
40: option reduces the report to special files
41: and files with set-user-ID mode;
42: it is intended to discover concealed violations
43: of security policy.
44: .PP
45: A file system must be specified.
46: .PP
47: The report is in no useful
48: order, and probably should be sorted.
49: .SH "SEE ALSO"
50: sort(1), dcheck(8), fsck(8), icheck(8)
51: .SH DIAGNOSTICS
52: When the filesystem structure is improper,
53: `??' denotes the `parent' of
54: a parentless file and
55: a pathname beginning with `...' denotes a loop.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.