1
.TH "ocfs2cdsl" "8" "February 2007" "Version @VERSION@" "OCFS2 Manual Pages"
3
ocfs2cdsl \- Create context dependent symbolic link (CDSL).
5
\fBocfs2cdsl\fR [\fB-cfnqvV\fR] [\fB\-t\fR \fIhostname|mach|os|nodenum\fR] \fIfilename\fR
8
\fBocfs2cdsl\fR is used to create a context dependent symbolic link for
9
\fIfilename\fR (file or directory) for a node. A CDSL \fIfilename\fR will
10
have its own image for a specific node, but a common name in the OCFS2. It
11
is very important that the \fBocfs2ctl\fR command to be issued on all nodes
12
that are part of the cluster and to any subsequent nodes that are added. If
13
the \fBocfs2cdsl\fR command is not executed in some of the nodes, the cdsl
14
directory will not be accessible by them.
19
\fB\-t\fR \fIhostname|mach|os|nodenum\fR
20
\fIhostname|mach|os|nodenum\fR - One of these options should be specified
21
in order to create the CDSL. As for information, \fIhostname\fR would be
22
the same as the output of "uname -n", \fImach\fR would be the output of
23
"uname -m", \fIos\fR would the the output of "uname -o" and \fInodenum\fR
24
would be the global node number for the hostname in the
25
\fI/etc/ocfs2/cluster.conf\fR file.
29
During the creation of the CDSL, if the file does exist, the data will be
30
copied to the new location.
34
Force the execution of the command.
38
Will perform a check of all options and motions, but will not perform any
43
Execute \fBocfs2cdsl\fR in quiet mode.
47
Execute \fBocfs2cdsl\fR in verbose mode.
51
Print version and exit.
55
If one wants to have a shared ORACLE_HOME installed on an OCFS2 partition,
56
and wants to have node specific configuration \fIfilename\fR in the same
57
shared ORACLE_HOME, one can have the \fIfilename\fR created by ocfs2cdsl.
58
A good example would be the directory $ORACLE_HOME/network/agent. Node1
59
could have its own view of the directory, which is different from Node2
60
view, but having the exact same full pathname.
63
# ocfs2cdsl -c -t hostname $ORACLE_HOME/network/agent
66
In the example above, a CDSL directory will be created and the contents of the
67
\fIagent\fR directory will copied to the new location. If the same is to be executed
68
on all nodes, and assuming that no changes are made to the directory, each one of the
69
nodes would have the exact same view of the \fIagent\fR directory. In case of change
70
in the \fIagent\fR directory after the creation of the CDSL, only the node performing
71
the change would be able to see it. All other nodes would still have the same initial
72
view of the \fIagent\fR directory.
86
Copyright \(co 2004, 2007 Oracle. All rights reserved.