Bug 850206

Summary: Introduce new systemd-rpm macros in mgetty spec file
Product: [Fedora] Fedora Reporter: Lukáš Nykrýn <lnykryn>
Component: mgettyAssignee: Michal Sekletar <msekleta>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 18CC: mrj, msekleta
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 14:50:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 850016    

Description Lukáš Nykrýn 2012-08-21 13:49:35 UTC
Fedora 18 changes the way how to work with services in spec files. It introduces new macros - %systemd_post, %systemd_preun and %systemd_postun; which replace scriptlets from Fedora 17 and older (see https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd, https://bugzilla.redhat.com/show_bug.cgi?id=850016).

Comment 1 Michal Sekletar 2013-03-19 15:59:15 UTC
Fixed in f19. Direct impact on user here is very low, not worth of pushing update. Closing as NEXTRELEASE.

Comment 2 mrj 2013-07-10 07:50:25 UTC
This Systemd macro works in Fedora 19. However mgetty started by Systemd fails to open the mgetty log file /var/log/mgetty.<device>.log due to the default F19 security policy.

Comment 3 Michal Sekletar 2013-07-10 15:02:43 UTC
(In reply to mrj from comment #2)
> fails to open the mgetty log file /var/log/mgetty.<device>.log due to the
> default F19 security policy.

Can you please provide some logs. I am unable to reproduce the issue. I am running with SELinux enabled in enforcing mode and mgetty can create log files just fine. Thanks.

Comment 4 Michal Sekletar 2013-07-31 14:50:44 UTC
If you are still experiencing the issue please file a new bug. Thanks.