diff -ur lcgdm-1.7.4.4.orig/common/Cgetopt.man lcgdm-1.7.4.4/common/Cgetopt.man
--- lcgdm-1.7.4.4.orig/common/Cgetopt.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/common/Cgetopt.man 2010-03-29 20:20:18.716732420 +0200
@@ -49,9 +49,9 @@
The
.B Cgetopt
function incrementally parses a command line argument list
-.BI argv
+.I argv
and returns the next known option character. An option character is known if it has been specified in the string of accepted option characters,
-.BI optstring .
+.IR optstring .
.P
The
.B Cgetopt_long
@@ -60,44 +60,45 @@
but it accepts options in two forms: words and characters. The
.B Cgetopt_long
function provides a superset of the functionality of
-.B Cgetopt
+.BR Cgetopt .
The additional functionality is described in the section CGETOPT_LONG.
.P
The option string
-.BI optstring
+.I optstring
may contain the following elements: individual characters, and characters followed by a colon to indicate an option argument is to follow. For example, an option string
.B x
recognizes an option
-.B x ,
+.BR -x ,
and an option string
.B x:
recognizes an option and argument
-.B x argument .
+.B -x
+.IR argument .
It does not matter to
.B Cgetopt
if a following argument has leading white space.
.P
On return from
-.BI Cgetopt ,
-.BI Coptarg
+.BR Cgetopt ,
+.I Coptarg
points to an option argument, if it is anticipated, and the variable
-.BI Coptind
+.I Coptind
contains the index to the next
-.BI argv
+.I argv
argument for a subsequent call to
-.B Cgetopt .
+.BR Cgetopt .
The variable
-.BI Coptopt
+.I Coptopt
saves the last known option character returned by
-.B Cgetopt .
+.BR Cgetopt .
.P
-The variable
-.BI Copterr
+The variables
+.I Copterr
and
-.BI Coptind
+.I Coptind
are both initialized to 1.
The
-.BI Coptind
+.I Coptind
variable may be set to another value before a set of calls to
.B Cgetopt
in order to skip over more or less argv entries.
@@ -105,11 +106,11 @@
In order to use
.B Cgetopt
to evaluate multiple sets of arguments, or to evaluate a single set of arguments multiple times, the variable
-.BI Coptreset
+.I Coptreset
must be set to 1 before the second and each additional set of calls to
-.B Cgetopt ,
+.BR Cgetopt ,
and the variable
-.BI Coptind
+.I Coptind
must be reinitialized.
.P
The
@@ -128,13 +129,13 @@
can be used in two ways. In the first way, every long option understood by the program has a coresponding short option, and the option structure is only used to translate from long option to short options. When used in this fashion,
.B Cgetopt_long
behaves identically to
-.B Cgetopt.
+.BR Cgetopt .
This is good way to add long option processing to an existing program with the minimum of rewriting.
.P
In the second mechanism, a long option set a flag in the
-.BI option
+.I Coptions_t
structure passed, or will store a pointer to the command line argument in the
-.BI option
+.I Coptions_t
structure passed to it for options that take arguments. Additionally, the long option's argument may be specified as a single argument with an equal sign, e.g
.B myprogram --myoption=somevalue
.P
@@ -165,31 +166,31 @@
.P
The
-.BI name
+.I name
field should contain the option name without the leading double dash.
.P
The
-.BI has_arg
-field should be one of
-.B NO_ARGUMENT
-no argument to the option is expect.
-.B REQUIRED_ARGUMENT
+.I has_arg
+field should be one of:
+.BR NO_ARGUMENT ,
+no argument to the option is expected.
+.BR REQUIRED_ARGUMENT ,
an argument to the option is required.
-.B OPTIONAL_ARGUMENT
+.BR OPTIONAL_ARGUMENT ,
an argument to the option may be presented.
.P
If
-.BI flag
+.I flag
is non-NULL, then the integer pointed to by it will set to the value in the
-.BI val
+.I val
field. If the
-.BI flag
+.I flag
field is NULL, then the
-.BI val
+.I val
field will be returned. Setting
-.BI flag
+.I flag
to NULL and setting
-.BI val
+.I val
to the corresponding short option will make this function act just
like
.B Cgetopt.
@@ -197,16 +198,16 @@
If the
.B Cgetopt
function encounters a character not found in the string
-.BI optstring
+.I optstring
or detects a missing option argument it writes an error message to
.B stderr
and returns
-.B ? .
+.BR ? .
Setting
-.BI Copterr
+.I Copterr
to a zero will disable these error messages.
If
-.BI optstring
+.I optstring
has a leading
.B :
then a missing option argument causes a
@@ -218,7 +219,7 @@
; this is reasonable but reduces the amount of error checking possible.
.SH CGETOPT_LONG EXTENSIONS
The
-.BI Coptreset
+.I Coptreset
variable was added to make it possible to call the
.B Cgetopt
function multiple times.
@@ -272,7 +273,7 @@
{"buffy", NO_ARGUMENT, NULL, 'b'},
{"floride", REQUIRED_ARGUMENT, NULL, 'f'},
{"daggerset", NO_ARGUMENT, &daggerset, 1},
- {NULL, 0, NULL, 0}
+ {NULL, 0, NULL, 0}
};
Coptind = 1; /* Required */
@@ -310,9 +311,7 @@
.SH HISTORY
The
.B Cgetopt
-function appeared
-.Bx 4.3 .
-The
+function appeared in BSD 4.3. The
.B Cgetopt_long
function first appeared in GNU libiberty. This implementation was imported to NetBSD from a Kerberos distribution.
.SH BUGS
@@ -324,12 +323,12 @@
.B -p1003.2-92
to decouple
.B Cgetopt
-from <stdio.h> .
+from <stdio.h>.
.P
A single dash
.B -
may be specified as an character in
-.BI optstring ,
+.IR optstring ,
however it should
.B never
have an argument associated with it.
@@ -340,7 +339,7 @@
as an option flag.
This practice is wrong, and should not be used in any current development.
It is provided for backward compatibility
-.B only .
+.BR only .
By default, a single dash causes
.B Cgetopt
to return -1.
@@ -354,7 +353,7 @@
as an option.
This practice is wrong, and should not be used in any current development.
It is provided for backward compatibility
-.B only .
+.BR only .
The following code fragment works in most cases.
.ft CW
.nf
@@ -382,7 +381,7 @@
.fi
.P
The
-.BI OPTIONAL_ARGUMENT
+.B OPTIONAL_ARGUMENT
always eats the following argument unless the argument is included via the
.B --option=argument
notation.
diff -ur lcgdm-1.7.4.4.orig/common/Cglobals.man lcgdm-1.7.4.4/common/Cglobals.man
--- lcgdm-1.7.4.4.orig/common/Cglobals.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/common/Cglobals.man 2010-03-29 20:20:18.717795403 +0200
@@ -45,7 +45,7 @@
.br
a \fB#define\fP macro that replaces all occurences of any global variable that needs to be thread-specific to this Cglobal's function.
.RE
-In order to satisfy packages not compiled with threads turned on, or that do not initialize \fBCASTOR\fP Thread Interface's \fBCthread\fP, any such global variable is also explicitely defined in \fBCglobals\fP.
+In order to satisfy packages not compiled with threads turned on, or that do not initialize \fBCASTOR\fP Thread Interface's \fBCthread\fP, any such global variable is also explicitly defined in \fBCglobals\fP.
.P
For example, taking the global error variable \fBserrno\fP, \fBCglobals\fP source code contains:
.RS
@@ -55,7 +55,7 @@
.RS
if \fBCglobals_init\fP was not (successfully) called, return the address of the global variable \fBserrno\fP
.br
-else return the adress of a thread-safe specific memory, instanciated at the first call to this function, that holds the content of the current instance of the thread-specific value of \fBserrno\fP
+else return the address of a thread-safe specific memory, instanciated at the first call to this function, that holds the content of the current instance of the thread-specific value of \fBserrno\fP
.RE
.RE
.P
@@ -67,11 +67,11 @@
.I getspec
function address that, given a static
.I key
-adress, returns the adress of a Thread-Specific memory into
+address, returns the address of a Thread-Specific memory into
.I addr
content. This uses an internal structure inside \fBCthread\fP, allocated on the heap, that is associated bijectively to
.I key
-address. \fBCthread\fP always explicitely allocates such internal structure to any
+address. \fBCthread\fP always explicitly allocates such internal structure to any
.I key
address if it is unknown at the moment of the call to
.I getspec.
@@ -97,7 +97,7 @@
.I addr
value, previously instanciated with a
.I getspec
-call, and possibly allocated on the heap by \fBCglobals\fP if necessary, will internally explicitely call the Operating System Thread-Specific functions that will put the value of
+call, and possibly allocated on the heap by \fBCglobals\fP if necessary, will internally explicitly call the Operating System Thread-Specific functions that will put the value of
.I address
as something thread-specific, bijectively associated to another member of the internal structure of \fBCthread\fP, itself bijective to
.I key.
@@ -119,7 +119,7 @@
.I addr
content, at return of \fBCglobals_get\fP, is not NULL, you can safely fill this memory with any value, provided you does not exceed the
.I size
-bytes length speficied in your previous call to \fBCglobals_get\fP. Because of applications that are \fBnot\fP multi-threaded, the initial value of
+bytes length specified in your previous call to \fBCglobals_get\fP. Because of applications that are \fBnot\fP multi-threaded, the initial value of
.I key
has then an importance, that's why it is necessary to always declare it with an initial value of -1.
.P
diff -ur lcgdm-1.7.4.4.orig/common/Cmutex.man lcgdm-1.7.4.4/common/Cmutex.man
--- lcgdm-1.7.4.4.orig/common/Cmutex.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/common/Cmutex.man 2010-03-29 20:20:18.717795403 +0200
@@ -28,7 +28,7 @@
.P
Please note that the \fBCmutex\fP package is initially meant to be interfaced with \fBCthread\fP only.
.P
-\fBCmutex_lock\fP takes as argument the adress
+\fBCmutex_lock\fP takes as argument the address
.BI addr
of anything that is static in your userspace, such as a 'static int variable;' address (see \fBEXAMPLE\fP section below), and a
.BI timeout
@@ -117,7 +117,7 @@
.nf
/*
* Here follows an example. The call to \fBCthread_init\fP routine shows
- * that multi-threaded mode is explicitely activated by the application
+ * that multi-threaded mode is explicitly activated by the application
* (you will then have to link with the thread library). Neverthless,
* you can very well call some other external library, and leave as it is
* the \fBCmutex\fP calls.
diff -ur lcgdm-1.7.4.4.orig/common/Cpool.man lcgdm-1.7.4.4/common/Cpool.man
--- lcgdm-1.7.4.4.orig/common/Cpool.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/common/Cpool.man 2010-03-29 20:20:18.717795403 +0200
@@ -24,7 +24,7 @@
\fBCpool\fP is a layer built upon \fBCthread\fP, the \fPCASTOR Thread\fP interface. It allows the user to create dedicated pools, and then to assign to one of them a given routine to execute.
.P
-The created processes or threads will remain alive, unless the routines assigned to are crashing, or explicitely calling an exit statement, like exit() or pthread_exit().
+The created processes or threads will remain alive, unless the routines assigned to are crashing, or explicitly calling an exit statement, like exit() or pthread_exit().
.P
Typical use might be writing a server, with a bunch of pre-created processes or pools (depending on the environment with which \fBCthread\fP has been compiled), and assign to a given pool a routine with the socket file descriptor as argument address.
.P
diff -ur lcgdm-1.7.4.4.orig/common/Csched.man lcgdm-1.7.4.4/common/Csched.man
--- lcgdm-1.7.4.4.orig/common/Csched.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/common/Csched.man 2010-03-29 20:20:18.718795389 +0200
@@ -98,7 +98,7 @@
.B not
mean that all those schedulings are supported on the platform you are running on. In particular, only
.I CSCHED_OTHER
-is officially supported everywhere. The other scheduling policies are totally system dependant and do not conform to any standardisation. Please be aware, also, that using a scheduling other than
+is officially supported everywhere. The other scheduling policies are totally system dependent and do not conform to any standardisation. Please be aware, also, that using a scheduling other than
.I CSCHED_OTHER
is an opendoor to processor deadlock...
.P
diff -ur lcgdm-1.7.4.4.orig/ns/Cns_access.man lcgdm-1.7.4.4/ns/Cns_access.man
--- lcgdm-1.7.4.4.orig/ns/Cns_access.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/ns/Cns_access.man 2010-03-29 20:20:18.724550373 +0200
@@ -46,7 +46,7 @@
.I amode
the bit pattern is built by an OR of the constants defined in
.RB < unistd.h >
-under Unix or to be explicitely defined under Windows/NT:
+under Unix or to be explicitly defined under Windows/NT:
.RS
.TP
.B R_OK
diff -ur lcgdm-1.7.4.4.orig/ns/Cns_accessr.man lcgdm-1.7.4.4/ns/Cns_accessr.man
--- lcgdm-1.7.4.4.orig/ns/Cns_accessr.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/ns/Cns_accessr.man 2010-03-29 20:20:18.724550373 +0200
@@ -45,7 +45,7 @@
.I amode
the bit pattern is built by an OR of the constants defined in
.RB < unistd.h >
-under Unix or to be explicitely defined under Windows/NT:
+under Unix or to be explicitly defined under Windows/NT:
.RS
.TP
.B R_OK
diff -ur lcgdm-1.7.4.4.orig/ns/Cns_startsess.man lcgdm-1.7.4.4/ns/Cns_startsess.man
--- lcgdm-1.7.4.4.orig/ns/Cns_startsess.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/ns/Cns_startsess.man 2010-03-29 20:20:18.724550373 +0200
@@ -17,12 +17,12 @@
starts session.
The connection to the Name Server is kept open until
.B Cns_endsess
-is explicitely called.
+is explicitly called.
Requests issued between
.B Cns_startsess
and
.B Cns_endsess
-are independant from each other and are individually committed or rolled back.
+are independent from each other and are individually committed or rolled back.
The
.I comment
is logged in the server log.
diff -ur lcgdm-1.7.4.4.orig/ns/Cns_starttrans.man lcgdm-1.7.4.4/ns/Cns_starttrans.man
--- lcgdm-1.7.4.4.orig/ns/Cns_starttrans.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/ns/Cns_starttrans.man 2010-03-29 20:20:18.724550373 +0200
@@ -20,7 +20,7 @@
.B Cns_aborttrans
or
.B Cns_endtrans
-is explicitely called.
+is explicitly called.
If all the DB update operations between
.B Cns_starttrans
and
diff -ur lcgdm-1.7.4.4.orig/rfio/rfio_access.man lcgdm-1.7.4.4/rfio/rfio_access.man
--- lcgdm-1.7.4.4.orig/rfio/rfio_access.man 2010-03-29 16:21:45.000000000 +0200
+++ lcgdm-1.7.4.4/rfio/rfio_access.man 2010-03-29 20:20:22.656552829 +0200
@@ -48,7 +48,7 @@
.I amode
the bit pattern is built by an OR of the constants defined in
.RB < unistd.h >
-under Unix or to be explicitely defined under Windows/NT:
+under Unix or to be explicitly defined under Windows/NT:
.RS
.TP
.B R_OK
diff -ur lcgdm-1.7.4.4.orig/rfio/rfio_readdir.man lcgdm-1.7.4.4/rfio/rfio_readdir.man
--- lcgdm-1.7.4.4.orig/rfio/rfio_readdir.man 2010-03-29 16:21:45.000000000 +0200
+++ lcgdm-1.7.4.4/rfio/rfio_readdir.man 2010-03-29 20:20:28.199552975 +0200
@@ -20,8 +20,8 @@
.SH DESCRIPTION
.B rfio_readdir
reads the directory opened by
-.B rfio_opendir
-. This routine returns a pointer to a structure containing the current directory
+.BR rfio_opendir .
+This routine returns a pointer to a structure containing the current directory
entry.
.TP
.I dirp
diff -ur lcgdm-1.7.4.4.orig/security/Csec_api.man lcgdm-1.7.4.4/security/Csec_api.man
--- lcgdm-1.7.4.4.orig/security/Csec_api.man 2010-03-29 16:21:47.000000000 +0200
+++ lcgdm-1.7.4.4/security/Csec_api.man 2010-03-29 20:20:28.199552975 +0200
@@ -76,7 +76,7 @@
framework for errors.
.sp
.TP
-.B "Csec_client_initContext,Csec_server_initContext,Csec_server_reinitContext
+.B Csec_client_initContext, Csec_server_initContext, Csec_server_reinitContext
Allow to initialize the
.B Csec_context_t
structure. The service type parameter defines which type of key will be used by the service. Its value can be:
@@ -96,7 +96,7 @@
A CASTOR tape host type key (e.g. castortape/machine_name@DOMAIN for KRB5) will be used
.RE
.TP
-.B Csec_client_establishContext,Csec_server_establishContext
+.B Csec_client_establishContext, Csec_server_establishContext
Given a initialized context and an opened socket, establishes a security context according to the chosen security mechanism.
.TP
.B Csec_client_setSecurityOpts, Csec_server_setSecurityOpts