Wiki . Forums . Bugs . Translation . Privacy Policy | Search . Simple . Advanced | Reports . Help | Matrix . 10.x . 11.x . 12.x . 13.x . Future . Recent . Contribs

Bug 7846 - Changes to smtpd instances are not activated by email-update event
Summary: Changes to smtpd instances are not activated by email-update event
Status: CLOSED FIXED
Alias: None
Product: SME Server Documentation
Classification: SME Server Extras
Component: Unknown (show other bugs)
Version: 9.0
Hardware: --- ---
: P3 normal
Target Milestone: ---
Assignee: SME Server Docteam
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2013-09-14 07:29 CEST by Michael McCarn
Modified: 2013-12-21 09:35 CET (History)
1 user (show)

See Also:
Package: ---
esmith: review?

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael McCarn 2013-09-14 07:29:27 CEST 
Changing smtpd Instances using
> config setprop smtpd Instances 30
> signal-event email-update

does not change the setting for the running instance of qpsmtpd.  

In order to get the new setting to take effect, you need to:
> sv t qpsmtpd

Looking in /etc/e-smith/events/email-update/services2adjust, I see:
> qpsmtpd -> sighup
> sqpsmtpd -> sighup

Should these be changed from "sighup" to "restart"?
Comment 6 Ian Wells 2013-12-21 09:35:08 CET 
(In reply to Michael McCarn from comment #5)
> If this looks OK, lets close this bug:
> > http://wiki.contribs.org/DB_Variables_Configuration#smtpd

Thanks for the fast update
Comment 5 Michael McCarn 2013-12-21 09:07:47 CET 
If this looks OK, lets close this bug:
> http://wiki.contribs.org/DB_Variables_Configuration#smtpd
Comment 4 Ian Wells 2013-12-20 19:15:11 CET 
(In reply to Charlie Brady from comment #3)
> (In reply to Michael McCarn from comment #0
> > Should these be changed from "sighup" to "restart"?
> 
> No. We don't want to shut down email any time anything is changed in the
> email settings.
> 
> Just do:
> 
> config setprop smtpd Instances 30
> expand-template /var/service/qpsmtpd/config
> sv t /service/qpsmtpd /service/sqpsmtpd
> 
> if you wish to change the number of instances.

So document only, no code change.
Comment 3 Charlie Brady 2013-12-20 18:09:29 CET 
(In reply to Michael McCarn from comment #0)
> Changing smtpd Instances using
> > config setprop smtpd Instances 30
> > signal-event email-update
> 
> does not change the setting for the running instance of qpsmtpd.  
> 
> In order to get the new setting to take effect, you need to:
> > sv t qpsmtpd
> 
> Looking in /etc/e-smith/events/email-update/services2adjust, I see:
> > qpsmtpd -> sighup
> > sqpsmtpd -> sighup
> 
> Should these be changed from "sighup" to "restart"?

No. We don't want to shut down email any time anything is changed in the email settings.

Just do:

config setprop smtpd Instances 30
expand-template /var/service/qpsmtpd/config
sv t /service/qpsmtpd /service/sqpsmtpd

if you wish to change the number of instances.
Comment 2 Ian Wells 2013-12-20 14:30:59 CET 
(In reply to Michael McCarn from comment #0)
> Changing smtpd Instances using
> > config setprop smtpd Instances 30
> > signal-event email-update
> 
> does not change the setting for the running instance of qpsmtpd.  
> 
> In order to get the new setting to take effect, you need to:
> > sv t qpsmtpd
> 
> Looking in /etc/e-smith/events/email-update/services2adjust, I see:
> > qpsmtpd -> sighup
> > sqpsmtpd -> sighup
> 
> Should these be changed from "sighup" to "restart"?

I don't know - so asking for further comment.
Comment 1 Ian Wells 2013-11-30 09:36:37 CET 
Toggling the review flag as I cannot answer Michael's question.