Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1260238 +++
--- Additional comment from Petr Lautrbach on 2016-07-19 15:20:07 EDT ---
You can use restorecon -vv if you need more verbose output:
# restorecon -vv /etc/machine-id
restorecon: /etc/machine-id not reset customized by admin to system_u:object_r:svirt_sandbox_file_t:s0
--- Additional comment from M. Scherer on 2016-07-19 15:39:35 EDT ---
I didn't knew there was 2 different level of verbosity, likely because that's neither in the man page, nor the --help output.
=============================
new matter:
the 'train track' summary at the top of the man page is:
SYNOPSIS
restorecon [-R] [-n] [-p] [-v] [-e directory] pathname...
restorecon -f infilename [-e directory] [-R] [-n] [-p] [-v] [-F]
as to the effect of the '-v' option, we see:
-n don't change any file labels (passive check). To display the
files whose labels would be changed, add -v.
-v show changes in file labels, if type or role are going to be
changed.
---------------
the problem:
I had no idea until reading this bug that a behavior undocumented in the 'man' page existed
The availability and the effect of multiple -v option repetition should be noted
As this is documentation,rather than function it is a low risk addition, and may well be an EASYFIX