HP Visualize J5000 hp enterprise file system: planning and configuring hp DCE/ - Page 40

cm gethardmount

Page 40 highlights

Installing and Configuring Enhanced DFS 3.0 Handling of setuid Programs and Device Files in DFS OUTPUT The cm gethardmount command first displays the line Fileset pathname status: In the output, pathname is the name of a file or directory specified with the -path option. For each specified file or directory, the following output values are possible for the fileset on which it resides: • hardmounted filesets allowed - Indicates that hard mount semantics are provided for this fileset. • hardmounted filesets not allowed - Indicates that hard mount semantics are not provided for this fileset. • cm: the fileset on which 'pathname' resides does not exist - Indicates that the specified pathname is invalid. EXAMPLES The following command indicates that hard mount semantics are not provided for the fileset that contains the directory /.../abc.com/fs/usr/jlw by the Cache Manager: $ cm gethardmount /.../abc.com/fs/usr/jlw Fileset /.../abc.com/fs/usr/jlw status: hardmounted filesets not allowed RELATED INFORMATION Commands: cm sethardmount(8dfs) 40

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164

40
Installing and Configuring Enhanced DFS 3.0
Handling of setuid Programs and Device Files in DFS
OUTPUT
The
cm gethardmount
command first displays the line
Fileset pathname status:
In the output,
pathname
is the name of a file or directory specified with the
-path
option.
For each specified file or directory, the following output
values are possible for the fileset on which it resides:
hardmounted filesets allowed - Indicates that hard mount semantics are provided
for this fileset.
hardmounted filesets not allowed - Indicates that hard mount semantics are not
provided for this fileset.
cm: the fileset on which ‘pathname’ resides does not exist - Indicates that the
specified pathname is invalid.
EXAMPLES
The following command indicates that hard mount semantics are not
provided for the fileset that contains the directory
/.../abc.com/fs/usr/jlw
by
the Cache Manager:
$ cm gethardmount /.../abc.com/fs/usr/jlw
Fileset /.../abc.com/fs/usr/jlw status: hardmounted filesets
not allowed
RELATED INFORMATION
Commands:
cm sethardmount(8dfs)