Fix up a few typos in the tree.

Signed-off-by: Chris Lalancette <clalance@redhat.com>
This commit is contained in:
Chris Lalancette 2009-09-22 11:42:06 +02:00
parent f4e74cf63c
commit 47c8709564
12 changed files with 17 additions and 17 deletions

View File

@ -59,4 +59,4 @@ for the associated RPC call.
While the helper method is executing, no locks are held on either
the client or server, but the ref count on the 'struct qemud_client'
object is incremented to ensure its not deleted. The helper can
now safely invoke the neccessary libvirt API call.
now safely invoke the necessary libvirt API call.

View File

@ -208,7 +208,7 @@
Thus, if a vendor / distributor has configured their libvirt package
to run as 'qemu' by default, a number of changes will be required
before an administrator can change a host to run guests as root.
In particular it will be neccessary to change ownership on the
In particular it will be necessary to change ownership on the
directories <code>/var/run/libvirt/qemu/</code>,
<code>/var/lib/libvirt/qemu/</code> and
<code>/var/cache/libvirt/qemu/</code> back to root, in addition

View File

@ -22,7 +22,7 @@
%endif
# Now set the defaults for all the important features, independant
# Now set the defaults for all the important features, independent
# of any particular OS
# First the daemon itself

View File

@ -1486,7 +1486,7 @@ esxDomainDestroy(virDomainPtr domain)
if (taskInfoState != esxVI_TaskInfoState_Success) {
ESX_ERROR(domain->conn, VIR_ERR_INTERNAL_ERROR,
"Could not destory domain");
"Could not destroy domain");
goto failure;
}

View File

@ -9423,7 +9423,7 @@ virStreamRef(virStreamPtr stream)
* Write a series of bytes to the stream. This method may
* block the calling application for an arbitrary amount
* of time. Once an application has finished sending data
* it should call virStreamFinish to wait for succesful
* it should call virStreamFinish to wait for successful
* confirmation from the driver, or detect any error
*
* This method may not be used if a stream source has been

View File

@ -780,7 +780,7 @@ openvzDomainDefineXML(virConnectPtr conn, const char *xml)
if (openvzSetInitialConfig(conn, vm->def) < 0) {
openvzError(conn, VIR_ERR_INTERNAL_ERROR,
"%s", _("Error creating intial configuration"));
"%s", _("Error creating initial configuration"));
goto cleanup;
}
@ -847,7 +847,7 @@ openvzDomainCreateXML(virConnectPtr conn, const char *xml,
if (openvzSetInitialConfig(conn, vm->def) < 0) {
openvzError(conn, VIR_ERR_INTERNAL_ERROR,
"%s", _("Error creating intial configuration"));
"%s", _("Error creating initial configuration"));
goto cleanup;
}

View File

@ -7915,7 +7915,7 @@ error:
* NB(4) This is very complicated. Due to connection cloning, multiple
* threads can want to use the socket at once. Obviously only one of
* them can. So if someone's using the socket, other threads are put
* to sleep on condition variables. THe existing thread may completely
* to sleep on condition variables. The existing thread may completely
* send & receive their RPC call/reply while they're asleep. Or it
* may only get around to dealing with sending the call. Or it may
* get around to neither. So upon waking up from slumber, the other

View File

@ -329,7 +329,7 @@ SELinuxSetFilecon(virConnectPtr conn, const char *path, char *tcon)
/* if the error complaint is related to an image hosted on
* an nfs mount, or a usbfs/sysfs filesystem not supporting
* labelling, then just ignore it & hope for the best.
* The user hopefully set one of the neccessary SELinux
* The user hopefully set one of the necessary SELinux
* virt_use_{nfs,usb,pci} boolean tunables to allow it...
*/
if (setfilecon_errno != EOPNOTSUPP) {

View File

@ -297,7 +297,7 @@ static int virClearCapabilities(void)
/*
* @conn Connection to report errors against
* @argv argv to exec
* @envp optional enviroment to use for exec
* @envp optional environment to use for exec
* @keepfd options fd_ret to keep open for child process
* @retpid optional pointer to store child process pid
* @infd optional file descriptor to use as child input, otherwise /dev/null

View File

@ -4761,7 +4761,7 @@ static virDrvOpenStatus vboxNetworkOpen(virConnectPtr conn,
(data->vboxSession == NULL))
goto cleanup;
DEBUG0("network intialized");
DEBUG0("network initialized");
/* conn->networkPrivateData = some network specific data */
return VIR_DRV_OPEN_SUCCESS;
@ -4770,7 +4770,7 @@ cleanup:
}
static int vboxNetworkClose(virConnectPtr conn) {
DEBUG0("network unintialized");
DEBUG0("network uninitialized");
conn->networkPrivateData = NULL;
return 0;
}
@ -5606,7 +5606,7 @@ static virDrvOpenStatus vboxStorageOpen (virConnectPtr conn,
(data->vboxSession == NULL))
goto cleanup;
DEBUG0("vbox storage intialized");
DEBUG0("vbox storage initialized");
/* conn->storagePrivateData = some storage specific data */
return VIR_DRV_OPEN_SUCCESS;
@ -5615,7 +5615,7 @@ cleanup:
}
static int vboxStorageClose (virConnectPtr conn) {
DEBUG0("vbox storage unintialized");
DEBUG0("vbox storage uninitialized");
conn->storagePrivateData = NULL;
return 0;
}

View File

@ -332,7 +332,7 @@ let isLockableDriverNull exp =
(*
* Prior to validating a function, intialize these
* Prior to validating a function, initialize these
* to VS.empty
*
* They contain the list of driver and object variables

View File

@ -275,10 +275,10 @@ exit 0
=head1 DESCRIPTION
This tool validates that the neccessary PKI files are configured for
This tool validates that the necessary PKI files are configured for
a secure libvirt server or client using the TLS encryption protocol.
It will report any missing certificate or key files on the host. It
should be run as root to ensure it can read all the neccessary files
should be run as root to ensure it can read all the necessary files
=head1 EXIT STATUS