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

Accessing DFS from an NFS Client, Unauthenticated Access to DFS

Page 154 highlights

The DFS/NFS Secure Gateway Configuring Gateway Server Machines The NFS client is now configured to provide access to DFS and to allow users of the client to authenticate to DCE with the dfs_login command. Repeat these steps on each NFS client to be configured in this manner. Accessing DFS from an NFS Client Once a Gateway Server machine and one or more NFS clients are configured according to the instructions in "Configuring Gateway Server Machine" and "Configuring NFS Clients to Access DFS", users of the NFS clients can access data in the DFS filespace. Users can access files and directories in DFS by full /.../cellname/fs pathnames or by abbreviated pathnames that use the /: link to the DFS filespace. The following are equivalent pathnames for the file myfile in the DFS filespace of the DCE cell abc.com: /.../abc.com/fs/myfile /:/myfile All users have unauthenticated access to DFS. Users who have DCE accounts can authenticate to their DCE identities for authenticated access to DFS. The following subsections provide more information about these two types of access. When accessing DFS data from a DFS client, the DFS Cache Manager caches local copies of files accessed from File Server machines. When accessing DFS data from an NFS client, NFS background I/O daemons cache local copies of files accessed via the NFS server. The caching of information by the NFS daemons can affect how quickly changes you make to data in DFS become visible to other users. Unauthenticated Access to DFS Unauthenticated access is provided to users who access DFS without first authenticating to DCE. For a user who does not have an account in the DCE registry database, unauthenticated access is the only form of access available. Unauthenticated access requires no preliminary steps; users simply access data in DFS from an NFS client. Unauthenticated users receive the following permissions for objects (files and directories) in the DFS filespace: 154

  • 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

154
The DFS/NFS Secure Gateway
Configuring Gateway Server Machines
The NFS client is now configured to provide access to DFS and to allow
users of the client to authenticate to DCE with the
dfs_login
command.
Repeat these steps on each NFS client to be configured in this manner.
Accessing DFS from an NFS Client
Once a Gateway Server machine and one or more NFS clients are configured
according to the instructions in “Configuring Gateway Server Machine” and
“Configuring NFS Clients to Access DFS”, users of the NFS clients can
access data in the DFS filespace. Users can access files and directories in
DFS by full
/.../
cellname
/fs
pathnames or by abbreviated pathnames that use
the
/:
link to the DFS filespace. The following are equivalent pathnames for
the file
myfile
in the DFS filespace of the DCE cell
abc.com
:
/.../abc.com/fs/myfile
/:/myfile
All users have unauthenticated access to DFS. Users who have DCE
accounts can authenticate to their DCE identities for authenticated access to
DFS. The following subsections provide more information about these two
types of access.
When accessing DFS data from a DFS client, the DFS Cache Manager
caches local copies of files accessed from File Server machines. When
accessing DFS data from an NFS client, NFS background I/O daemons
cache local copies of files accessed via the NFS server. The caching of
information by the NFS daemons can affect how quickly changes you make
to data in DFS become visible to other users.
Unauthenticated Access to DFS
Unauthenticated access is provided to users who access DFS without first
authenticating to DCE. For a user who does not have an account in the DCE
registry database, unauthenticated access is the only form of access
available.
Unauthenticated access requires no preliminary steps; users
simply access data in DFS from an NFS client.
Unauthenticated users receive the following permissions for objects (files
and directories) in the DFS filespace: