Bug 696008 - Sendmail stopped updating maillog
Summary: Sendmail stopped updating maillog
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sendmail
Version: 5.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-13 03:58 UTC by Simon Gao
Modified: 2012-03-06 09:45 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-06 09:45:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Simon Gao 2011-04-13 03:58:21 UTC
Description of problem:

Sendmail stopped updating /var/log/maillog. 


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

sendmail-8.13.8-8.el5.x86_64
kernel 2.6.18-194.32.1.el5xen

How reproducible:


Steps to Reproduce:
1. Install sendmail
2. Make change to /etc/sendmail.mc and generate sendmail.cf
3. Restart sendmail daemon
  
Actual results:

Sendmail stopped updating /var/log/maillog. Also subsequent changes to sendmail.cf no longer worked. Only reboot the machine will make the problem go away.

Expected results:

Sendmail should be able to update /var/log/maillog across sendmail.cf changes and sendmail restart.


Additional info:

Comment 1 Jaroslav Škarvada 2011-04-22 14:32:25 UTC
I am unable to reproduce, tested on two cleanly provisioned 5.6 machines:
sendmail-8.13.8-8.el5.x86_64
kernel-2.6.18-238.el5.x86_64
kernel-xen-2.6.18-238.el5.x86_64

(tested with, w/o xen kernel)

steps:
1. yum install sendmail-cf
2. updated /etc/mail/sendmail.mc
3. make sendmail.cf
4. service sendmail restart

Step 3 can be omitted, because the config is automatically regenerated upon restart.

Can you retest on 5.6 / provide more information?

Comment 2 Jaroslav Škarvada 2012-03-06 09:45:05 UTC
I was unable to reproduce and I don't have not enough information thus closing as cantfix.


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