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.
Basically the same inquiry has been reported at
https://bugzilla.redhat.com/show_bug.cgi?id=1018335
[various timing parameters have an incorrect USec suffix in systemctl show output, such as RestartUSec, TimeoutUSec, etc.]
But I would like some feedback about it, as it is
confusing to need to set TimeoutStartSec and when
querying values it shows TimeoutStartUSec. Yet, also
confusing is the fact that it is required to tell,
and it also outputs, time units, i.e. "min" for minutes
and "s" for seconds.
I am not sure that I can tell you more than Lennart already wrote in the mentioned bug.
TimeoutStartSec in the unit file make sense because it is created by the user and it is practical to have seconds as a default value there.
In the other hand internally we use microseconds because that gives us better granularity. systemctl show is a low level command to display the internal things.
Maybe it would be better to display the time in microseconds in the show output, instead of converting them to human-readable values. But we are providing stability promise on output of systemctl show (so it can be used in scripts), so it is really hard to change that.