DC 2 QA Unit III
DC 2 QA Unit III
DC 2 QA Unit III
UNIT III
File Length
Creation Time stamp
Read Timestamp
Write time stamp
Attribute time stamp
Reference count
Owner
File Type
Operations: fieldes=open(name,mode)
fieldes=create(name,mode)
status=close(fieldes)
count=read(fieldes,buffer,n)
count=write(fieldes,buufer,n)
pos=Iseek(filedes,offset,whence)
status=unlink(nmae)
status=link(name1,nmae2)
status=stat(name,buffer)
i. Access transparency
ii. Location transparency
iii. Mobility transparency
iv. Performance transparency
v. Scaling transparency
Changes to a file by one client should not interfere with the operation of other clients
simultaneously accessing or changing the same file. This is well-known issue of concurrency
control .The need for concurrency control for accss to shared data in many applications Is
widely accepted and techniques are known for its implementation ,but they are costly .Most
current file services follow morden UNIX standards in providing advisery or mandatoryfile or
record-level locking.
In a file service that supports replication, a file may be represented by several copies of its
contents at different locations. This has two benefits-its enables multiple servers to share the load
of providing a service to clients accessing the same set of files, enhancing the scalability of the
service, and it enhances fault tolerance by enabling clients to locate another server that holds a
copy of the file when one has failed. Few file services support replication fully, but most support
the catching of files or portions of files locally, a limited form of replication.
The directory services provide a mapping between text names for files and their UFIDs. Client
may obtain the UFIDs of a file by quoting its text name to the directory services. The directory
services provides the function needed to generate directories, to add new file name to directories
and to obtain UFIDs from directories. It is client of the flat file services; its directory is stored in
files of the flat services. When a hierarchic file-naming scheme is adopted as in UNIX,
directories hold references to other directories.
Lookup(Dir,Name)→FileID –throws not found Locate the text name in the directory and returns
the relevant UFID.If name is not in the
directory, throws an exception
UnName (Dir,Name)—throws not found If name is in the directory: The entry containing
name is removed from the directory.
If name is not in the directory;throws an
exception.
The name is resolved when it is translated into data about the named resource or object, often in
order to invoke an action upon it. The association between a name and an object is called a
binding. In general, names are bound to attributes of the named objects, rather than the
implementation of the objects themselves. An attribute is the value of a property associated with
an object.
URI-Uniform Resource Identifiers came about from the need to identify resources on the web,
and other internet resources such as electronic mailboxes. An important goal was to identify
resources in a coherent way, so that they could all be processed by common software such as
browser. URIs is ‘uniform’ in that their syntax incorporates that of indefinitely many individual
types of resource identifier(i.e URI schemas),and there are procedures for managing the global
namespace of schemas. The advantage of uniformity is that eases the process of introducing new
types of identifier, as well as using existing types of identifier in new contexts without
disrupting existing usage.
Uniform Resource Names are URIs that are used as pure resource names rather than locators.
Mid:0E4FC272-5C02-11D9-B115-000A95B55BC8@hpl.hp.com
Is a URN that identifies the email message containing it in its ‘message-id’ field. The URI
distinguishes that message from any other email message. But it does not provide the message’s
address in any store, so a lookup operation is needed to find it.
The Global name Service developed at the Digital Equipment corporation systems, Research
Center,is a descentdant of Grapevine with ambitious goals, including:
The process of locating naming data from than more than one name server in order to resolve a
name is called navigation. The client name resolution software carries out navigation on behalf
of the client. It communicates with name servers as necessary to resolve a name.
In multicast navigation, a client multicast the name to be resolved and required object type to the
group of name servers. Only the server that holds the named attributes responds to the request.
Unfortunately, however, if the name proves to be unbound, the request is greeted with silence.
One navigation model that DNS supports is known as iterative navigation. To resolve a name, a
client present the name to the local name server, which attempts to resolve it. If the local name
server has the name, it returns the result immediately. If it does not it will suggest another server
that will ba able to help. Resolution proceeds at the new server, with further navigation as
necessary until the name is located or is discovered to be unbounded.
In the non recursive and non recursive server controlled navigation. Under non recursive server
controlled navigation ,any name server may be chosen by the client. This server communicates
by multicast or iteratively with its peer in the style described above, as through it were a client.
Under recursive server-controlled navigation ,the client once more contacts a single server. If
this server doesnot store the name,the server contains a peer to storing a prefix of the
name,which in turn attempts to resolve it. This procedure continues recursively until the name
resolved.
This original scheme was soon seen to suffer from three major shortcomings:
The domain name system is a name service design whose main naming database is used across
the internet. It was devised principally by mockapetris and specified in RFC 1034 and RFC
1035. DNS replaced the original internet naming scheme in which all host names and address
were held in a single central master file and downloaded by FTP to all computer that required
them.
Domain Names: The DNS is designed for use in multiple implementations, each of which may
have its own name space. In practice, however, only one is in widespread use, and that is one
used for naming across the internet. The internet DNS name space is partitioned both
organizationally and according to geography. The names are written with the highest-level
domain on the right. The original top-level organizational domains in use across the internet
were:
The DNS naming data are divided into zones. A zone contains the following data:
Attributes data for names in a domain, less any subdomains administrates by lower level
authorities.
The names and address of at least two name servers that provide authoritative data for the
zone. These are versions of zone data that can be relied upon as being reasonably up to
date.
The names of name servers that hold authoritative data for delegated sub domains; and
‘glue’ data giving the IP address of these servers.
Zone-management parameters, such as those governing the catching and replication of
zone data.
Data in write operation received from client is stored in the memory cache at the server and
written to disk before a reply is sent to the client. This is called writethrough caching. The client
can be sure that is data stored persistently as soon as reply has been received.
Data in write operation is stored only in the memory cache. It will be written to disk when a
commit operation is received for the relevant file. The client can be sure that the data is persistent
stored only when a reply to a commit operation for the relevant file has been received. Standard
NFS clients use this mode of operation, issuing a commit whenever a file that was open for
writing is closed.
The Berkeley internet name domain is an implementation of the DNS for computers running
UNIX. Client programs link in library software as the resolver. DNS name server computers run
the named deamon. BIND allows for three categories of name server: primary server, secondary
yserver, caching only servers. The named program implements just one of these types, according
to the content of a configuration file. Caching only servers read in form a configuration file
sufficient names and address of authoritative servers to resolve any name. Thereafter, they only
store this data and data they learn by resolving names for clients.
Name management is separated from other service largely because of the openness of distributed
system, which brings the following motivation:
Unification
Integration
A namespace is the collection of all valid names recognized by a particular service. The service
will attempt to look up a valid name, even though that name may prove not to correspond to any
object. Name space requires a syntactic definition to separate.
PART B
Napster’s architecture included centralized indexes, but users supplied the files,
which were stored and accessed on their personal computers.
Limitations: Napster used a (replicated) unified index of all available music files. For the
application in question, the requirement for consistency between the replicas was not
strong, so this did not hamper performance, but for many applications it would constitute
a limitation. Unless the access path to the data objects is distributed, object discovery and
addressing are likely to become a bottleneck
Application dependencies
• Music files are never updated, avoiding any need to make sure all the replicas of files
remain consistent after updates.
• No guarantees are required concerning the availability of individual files – if a music
file is temporarily unavailable, it can be downloaded later. This reduces the requirement
for dependability of individual computers and their connections to the Internet.
Directory cache
Prefix cache
Full name cache
Multicache consistency
Immediate Invalidate
On-Use Update
5. Describe LDAP
LDAP stands for Lightweight Directory Access Protocol Access Protocol. LDAP
defines a standard method for accessing and updating information in a directory.
LDAP uses:
Centrally manage users, groups and other data
Don’t have to manage separate directories for each application
Allows users to find data that they need.
Not locked into a particular server.