From 47c8709564ac3f2ec5b4a3830ac213e69b4a44d5 Mon Sep 17 00:00:00 2001 From: Chris Lalancette Date: Tue, 22 Sep 2009 11:42:06 +0200 Subject: [PATCH] Fix up a few typos in the tree. Signed-off-by: Chris Lalancette --- daemon/THREADING.txt | 2 +- docs/drvqemu.html.in | 2 +- libvirt.spec.in | 2 +- src/esx/esx_driver.c | 2 +- src/libvirt.c | 2 +- src/openvz/openvz_driver.c | 4 ++-- src/remote/remote_driver.c | 2 +- src/security/security_selinux.c | 2 +- src/util/util.c | 2 +- src/vbox/vbox_tmpl.c | 8 ++++---- tests/object-locking.ml | 2 +- tools/virt-pki-validate.in | 4 ++-- 12 files changed, 17 insertions(+), 17 deletions(-) diff --git a/daemon/THREADING.txt b/daemon/THREADING.txt index 4c7a616614..4be71d63ad 100644 --- a/daemon/THREADING.txt +++ b/daemon/THREADING.txt @@ -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. diff --git a/docs/drvqemu.html.in b/docs/drvqemu.html.in index dd89fc3279..024835cfdb 100644 --- a/docs/drvqemu.html.in +++ b/docs/drvqemu.html.in @@ -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 /var/run/libvirt/qemu/, /var/lib/libvirt/qemu/ and /var/cache/libvirt/qemu/ back to root, in addition diff --git a/libvirt.spec.in b/libvirt.spec.in index 7b5c4d77cc..e02e58897a 100644 --- a/libvirt.spec.in +++ b/libvirt.spec.in @@ -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 diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c index 5754b24aa1..ec0cc146a9 100644 --- a/src/esx/esx_driver.c +++ b/src/esx/esx_driver.c @@ -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; } diff --git a/src/libvirt.c b/src/libvirt.c index 27d761d5dd..4cc19ec311 100644 --- a/src/libvirt.c +++ b/src/libvirt.c @@ -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 diff --git a/src/openvz/openvz_driver.c b/src/openvz/openvz_driver.c index 54bcaa9fd5..d577be1d2e 100644 --- a/src/openvz/openvz_driver.c +++ b/src/openvz/openvz_driver.c @@ -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; } diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c index 135b0d6c65..731b2139ec 100644 --- a/src/remote/remote_driver.c +++ b/src/remote/remote_driver.c @@ -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 diff --git a/src/security/security_selinux.c b/src/security/security_selinux.c index 670fcb28dd..bdd9eb2a93 100644 --- a/src/security/security_selinux.c +++ b/src/security/security_selinux.c @@ -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) { diff --git a/src/util/util.c b/src/util/util.c index ef07a6a57c..f474ead9d6 100644 --- a/src/util/util.c +++ b/src/util/util.c @@ -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 diff --git a/src/vbox/vbox_tmpl.c b/src/vbox/vbox_tmpl.c index 154859a3e7..72220e10fd 100644 --- a/src/vbox/vbox_tmpl.c +++ b/src/vbox/vbox_tmpl.c @@ -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; } diff --git a/tests/object-locking.ml b/tests/object-locking.ml index 0c66fc7cf9..a4cd77d7e7 100644 --- a/tests/object-locking.ml +++ b/tests/object-locking.ml @@ -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 diff --git a/tools/virt-pki-validate.in b/tools/virt-pki-validate.in index f3d3218481..a428a96474 100755 --- a/tools/virt-pki-validate.in +++ b/tools/virt-pki-validate.in @@ -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