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.
Bug 1165391 - sendmail fail if restart quick after start
Summary: sendmail fail if restart quick after start
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sendmail
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-18 21:00 UTC by Radka Brychtova
Modified: 2018-11-16 13:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1650552 (view as bug list)
Environment:
Last Closed: 2018-11-16 13:42:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Jaroslav Škarvada 2014-11-20 09:54:54 UTC
I am afraid this is unfixable (or more precisely not worth the fix) at the moment.

There are two systemd services bind together, both forking. The PID file is written in the child process, not the parent, that's why systemd has to use notify + timeout to get the PID file.

In the past we tried:
a) moving write PID from the child to the parent process
b) patching sendmail to provide same functionality in the non daemon mode as in the daemon mode and switching systemd services to non-forking mode

Both weren't trivial patches and both were rejected upstream. Not counting that fast consecutive restarts of mail server aren't typical use case.

Comment 8 Red Hat Bugzilla Rules Engine 2018-11-16 13:42:50 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.


Note You need to log in before you can comment on or make changes to this bug.