postfix problem with systemd

Ed Greshko Ed.Greshko at greshko.com
Sat Jun 16 02:39:48 UTC 2012


On 06/16/2012 10:11 AM, Ed Greshko wrote:
> On 06/16/2012 09:55 AM, Jeff Gipson wrote:
>> On Sat, Jun 16, 2012 at 02:13:00AM +0200, Chris wrote:
>>> 2012/6/16 Jeff Gipson <jeffagipson at gmail.com>:
>>>> What is the output of
>>>>  rpm -q -f /etc/postfix/chroot-update
>>> rpm -q -f /etc/postfix/chroot-update
>>> error: file /etc/postfix/chroot-update: No such file or directory
>>>
>>> -- 
>>> Chris
>>> -- 
>>> users mailing list
>>> users at lists.fedoraproject.org
>>> To unsubscribe or change subscription options:
>>> https://admin.fedoraproject.org/mailman/listinfo/users
>>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>>> Have a question? Ask away: http://ask.fedoraproject.org
>>     ### End of Message from Chris ###
>>
>> Sounds like the error message is quite accurate... that file doesn't exist...
>>
>> What about
>> rpm -q -f /usr/lib/systemd/system/postfix.service look like?
>>
> FWIW, I normally run sendmail...  But, since my F17.i686 system is for "playing" I
> stopped sendmail, disabled it via systemct and then installed postfix.
>
> I then did an "enable" and "start" of postfix and it started with the default
> configuration without problems.  There is no /etc/postfix/chroot-update.
>
> Also, "yum whatprovides /etc/postfix/chroot-update" returns nothing.
>
> There is a shell script (/usr/share/doc/postfix-2.9.2/examples/chroot-setup/LINUX2)
> but even that doesn't appear to reference a /etc/postfix/chroot-update file.
>

You know....  I really should run the command from the OP....

[root at f17 ~]# service postfix status
Redirecting to /bin/systemctl  status postfix.service
postfix.service - Postfix Mail Transport Agent
          Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled)
          Active: active (running) since Sat, 16 Jun 2012 10:01:55 +0800; 35min ago
         Process: 3239 ExecStart=/usr/sbin/postfix start (code=exited, status=0/SUCCESS)
         Process: 3238 ExecStartPre=/etc/postfix/chroot-update (code=exited,
status=203/EXEC)
         Process: 3233 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited,
status=0/SUCCESS)
        Main PID: 3310 (master)
          CGroup: name=systemd:/system/postfix.service
                  ├ 3310 /usr/libexec/postfix/master
                  ├ 3311 pickup -l -t fifo -u
                  └ 3312 qmgr -l -t fifo -u

So, while the postfix process is running just fine one does get the message about
/etc/postfix/chroot-update .

So.....  My conclusion is that this is an "expected" message.

Active: active (running) is really the important thing....and the service is running
correctly.... Yes?

-- 
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage


More information about the users mailing list