Bug 959691

Summary: /usr/libexec/postfix/chroot-update show a failure by default in systemd output
Product: [Fedora] Fedora Reporter: Michael S. <misc>
Component: postfixAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cfergeau, jskarvad
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-22 07:50:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael S. 2013-05-04 20:27:21 UTC
Running systemctl status postfix show a error message with default configuration :

[root@liliana misc]# systemctl status postfix
postfix.service - Postfix Mail Transport Agent
   Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled)
   Active: active (running) since sam. 2013-05-04 22:00:16 CEST; 24min ago
  Process: 31091 ExecStop=/usr/sbin/postfix stop (code=exited, status=0/SUCCESS)
  Process: 31107 ExecStart=/usr/sbin/postfix start (code=exited, status=0/SUCCESS)
  Process: 31104 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited, status=1/FAILURE)
  Process: 31101 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited, status=0/SUCCESS)
 Main PID: 31179 (master)
   CGroup: name=systemd:/system/postfix.service
           ├─31179 /usr/libexec/postfix/master -w
           ├─31180 pickup -l -t unix -u
           └─31181 qmgr -l -t unix -u


While everything is working fine, it would be cleaner to not fail, as this could make sysadmin wonder if something wrong is going on. ( but adding "exit 0" would then hide errors, so that's not good either )

Comment 1 Christophe Fergeau 2013-05-22 07:45:39 UTC
Looks like a duplicate of bug #917463

Comment 2 Michael S. 2013-05-22 07:50:06 UTC

*** This bug has been marked as a duplicate of bug 917463 ***