Bug 1229291 - remove executable permission bits from pki-tomcatd.target
Summary: remove executable permission bits from pki-tomcatd.target
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pki-core
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Harmsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-08 11:52 UTC by Lukas Slebodnik
Modified: 2020-10-04 21:04 UTC (History)
4 users (show)

Fixed In Version: pki-core-10.3.1-1.fc24
Clone Of:
Environment:
Last Closed: 2016-07-19 14:42:18 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 2288 0 None None None 2020-10-04 21:04:36 UTC

Description Lukas Slebodnik 2015-06-08 11:52:02 UTC 
Reported by journalctl

systemd[1]: Configuration file /usr/lib/systemd/system/pki-tomcatd.target is marked executable. Please remove executable permission bits. Proceeding anyway.
Configuration file /lib/systemd/system/pki-tomcatd@.service is marked executable. Please remove executable permission bits. Proceeding anyway.

It's spamming my journal. Could you please remove the executable bit.
Thank you in advance
Comment 1 Matthew Harmsen 2016-01-13 00:33:46 UTC 
Upstream ticket:
https://fedorahosted.org/pki/ticket/1730
Comment 2 Fedora End Of Life 2016-07-19 14:42:18 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.