Bug 69468 - The initscripts of Postfix and Sendmail don't seem to be aware of each other
Summary: The initscripts of Postfix and Sendmail don't seem to be aware of each other
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: sendmail
Version: limbo
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Florian La Roche
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-22 18:56 UTC by Peter van Egdom
Modified: 2007-04-18 16:44 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-07-22 18:56:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Peter van Egdom 2002-07-22 18:56:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020719

Description of problem:
When I first start Postfix with "/etc/rc.d/init.d/postfix start"
and then start Sendmail with "/etc/rc.d/init.d/sendmail start"

both seem to start, while Postfix is the SMTP server :

  [root@limbo-hp root]# fuser smtp/tcp
  smtp/tcp:             7621
  [root@limbo-hp root]# ps -ax |grep 7621
   7621 ?        S      0:00 /usr/libexec/postfix/master

However, after stopping both services, when I do :

First start Sendmail with "/etc/rc.d/init.d/sendmail start"
and then start Postfix with "/etc/rc.d/init.d/postfix start"

The Postfix initscript says [  OK  ], while it seems not to have been
started.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.see description
2.
3.
	

Actual Results:  Both Sendmail and Postfix initscripts give [  OK  ] after
starting both of them. 

When Sendmail is first started, Postfix is not to be seen in the process list
(ps -ax |grep postfix), although Postfix reports [  OK  ] when started with
"/etc/rc.d/init.d/postfix start".

When Postfix is first started, Sendmail actually is seen running in the process
list (ps -ax |grep sendmail). 


Expected Results:  I would've expected some consistency, maybe a check of what 
daemon is running on port 25, and starting the other would give, for example,
the warning :

 "... another SMTP server running, [ FAIL ]".

Additional info:

[root@limbo-hp postfix]# /etc/rc.d/init.d/postfix start
Starting postfix:                                          [  OK  ]
[root@limbo-hp postfix]# /etc/rc.d/init.d/sendmail start
Starting sendmail:                                         [  OK  ]
Starting sm-client:                                        [  OK  ]
[root@limbo-hp postfix]# fuser smtp/tcp
smtp/tcp:             9434
[root@limbo-hp postfix]# ps -ax |grep 9434
 9434 ?        S      0:00 /usr/libexec/postfix/master
[root@limbo-hp postfix]# ps -ax |grep sendmail
 9468 ?        S      0:00 /usr/sbin/sendmail -bd -q1h
 9479 ?        S      0:00 sendmail: Queue runner@01:00:00 for /var/spool/client
[root@limbo-hp postfix]# /etc/rc.d/init.d/sendmail stop
Shutting down sendmail: /etc/rc.d/init.d/sendmail: kill: (9479) - Onbekend proces
                                                           [  OK  ]
Shutting down sm-client:                                   [FAILED]
[root@limbo-hp postfix]# /etc/rc.d/init.d/postfix stop
Shutting down postfix:                                     [  OK  ]
[root@limbo-hp postfix]# /etc/rc.d/init.d/sendmail start
Starting sendmail:                                         [  OK  ]
Starting sm-client:                                        [  OK  ]
[root@limbo-hp postfix]# /etc/rc.d/init.d/postfix start
Starting postfix:                                          [  OK  ]
[root@limbo-hp postfix]# fuser smtp/tcp
smtp/tcp:      9568
[root@limbo-hp postfix]# ps -ax |grep 9568
 9568 ?        S      0:00 sendmail: accepting connections
[root@limbo-hp postfix]# ps -ax |grep postfix
[root@limbo-hp postfix]#

Comment 1 Bill Nottingham 2002-07-23 03:21:21 UTC
Don't do that. You should use alternatives/redhat-switchmail to configure your
chosen mail daemon.


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