Bug 19367 - Failure to restart sendmail
Summary: Failure to restart sendmail
Status: CLOSED DUPLICATE of bug 20696
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts   
(Show other bugs)
Version: 7.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2000-10-19 04:35 UTC by Jon Benson
Modified: 2014-03-17 02:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-10-19 04:36:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jon Benson 2000-10-19 04:35:59 UTC
When using "/etc/rc.d/init.d/sendmail restart" which is basically a stop
followed by a start it fails.

The fault can be looked at in one of two ways.

1. The stop being at fault:
It only kills the original sendmail server process and will leave other
sendmail proccess around to complete sending/receiving mail.  This is
actually desired behaviour IMHO.

This means the start process finds a sendmail process running and refuses
to start the server.

2. The start proccss being at fault:
The start process perhaps needs to pass an optional extra argument or
employ some method such that it can search for a certain instance of a

Eg. in the case of sendmail the process that is relevant to the restart is
the one accepting connections which appears as follows when doing a "ps
sendmail: accepting connections

Hence there exists the opportunity to test for a process that has both the
process name of sendmail and contains the key information "accepting

I hope this makes sense as it is certainly a feature I'd love to see fixed
as we regularly restart our mail server after various configuration

Comment 1 Bill Nottingham 2000-11-13 20:46:20 UTC

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

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