shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 17:34:18 +03:00
Code Releases Activity

Fix typo in manpage

Browse Source 
It's "service libvirtd start", not "service start libvirtd".

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
This commit is contained in:
Mark McLoughlin 2009-04-20 11:55:53 +00:00
parent 55671efe80
commit a4b1c0977a
3 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -1,3 +1,7 @@
Mon Apr 20 12:54:02 GMT 2009 Mark McLoughlin <markmc@redhat.com>
* docs/virsh.pod, virsh.1: fix typo reported by Robert P. J. Day
Mon Apr 20 11:24:23 CEST 2009 Daniel Veillard <veillard@redhat.com>
* po/*: merge in a lot of localization updates and regenerate

2
docs/virsh.pod
View File

@ -34,7 +34,7 @@ the program.
All B<virsh> operations rely upon the libvirt library.
For any virsh commands to run xend/qemu, or what ever virtual library that libvirt supports. For this reason you should start xend/qemu as a service when your system first boots using xen/qemu. This can usually be done using the command
B<service start libvirtd> .
B<service libvirtd start> .
Most B<virsh> commands require root privileges to run due to the
communications channels used to talk to the hypervisor. Running as

2
virsh.1
View File

@ -171,7 +171,7 @@ the program.
.IX Header "NOTES"
All \fBvirsh\fR operations rely upon the libvirt library.
For any virsh commands to run xend/qemu, or what ever virtual library that libvirt supports. For this reason you should start xend/qemu as a service when your system first boots using xen/qemu. This can usually be done using the command
\&\fBservice start libvirtd\fR .
\&\fBservice libvirtd start\fR .
.PP
Most \fBvirsh\fR commands require root privileges to run due to the
communications channels used to talk to the hypervisor. Running as