Description of problem: Typo error in virt-tail man page: EXAMPLE Follow /var/log/messages inside a virtual machine called "mydomain": virt-tail -d mydomain /etc/fstab The “/var/log/messages” should be consistent with "/etc/fstab". Version-Release number of selected component (if applicable): libguestfs-1.34.3-2.el7.x86_64 >From repo: https://people.redhat.com/~rjones/libguestfs-RHEL-7.4-preview/ How reproducible: 100% Steps: Actual results: Expected results: Additional info:
I'm somewhat confused what the problem is here. Can you describe exactly what is the issue? In any case, the original POD markup is correct: =head1 EXAMPLE Follow F</var/log/messages> inside a virtual machine called C<mydomain>: virt-tail -d mydomain /etc/fstab
(In reply to Richard W.M. Jones from comment #1) > I'm somewhat confused what the problem is here. Can you describe > exactly what is the issue? > > In any case, the original POD markup is correct: > > =head1 EXAMPLE > > > > Follow F</var/log/messages> inside a virtual machine called C<mydomain>: > > > > virt-tail -d mydomain /etc/fstab Shouldn't the “/var/log/messages” be consistent with "/etc/fstab"? The example is saying that follow the file : /var/log/mesages, but the command line you use /etc/fstab , I think that would confuse the user.
/etc/fstab is in a verbatim section. It all looks good in the HTML version: http://libguestfs.org/virt-tail.1.html#example I don't really think this is a bug. It's just that the text-based man page output doesn't have enough formatting available to show verbatim sections in a different font.
Rich: the issue is that the man page says "see how you can monitor /var/log/messages", but the example for it (which follows) mentions /etc/fstab.
Oh I see ... yes, this is a bug, patch posted: https://github.com/libguestfs/libguestfs/commit/2643c4d5f425b216d0d3fadee8f0f4ed69cfafba
Verify with packages: libguestfs-1.36.2-3.el7.x86_64 Steps: 1. # man virt-tail ... ... EXAMPLE Follow /var/log/messages inside a virtual machine called "mydomain": virt-tail -d mydomain /var/log/messages So verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2023