Issue #2699 has been updated by Peter Meier.

> I held off on adding any 'legacy' comments to the sysconfig files for now.  
> Is it even possible to do the equivalent of:
> 
> [...]
> 
> outside of the puppetmaster sysconfig file?

no, because if PUPPETMASTER_PORTS is defined and an array the init.d script 
will automagically start multiple master processes using mongrel, which is the 
whole idea behind this feature.

> Perhaps a note like this would suffice:
> 
> [...]
> 
> ?

maybe yes. Maybe it will also raise confusion, which one is treated with 
priority, as the sysconfig are passed as cli-switches. But generally I agree to 
reduce them to the minimum.
----------------------------------------
Bug #2699: Configurable port in the included Red Hat init script is broken
http://projects.reductivelabs.com/issues/2699

Author: Matthias Saou
Status: Ready for Checkin
Priority: Normal
Assigned to: Todd Zullinger
Category: Red Hat
Target version: 0.25.1
Affected version: 0.25.1rc1
Keywords: 
Branch: git://jet.mox.net/~tmz/puppet.git tickets/0.25.x/2699


The conf/redhat/client.init file uses the --port option to try and set the 
puppetmaster port, but this option is not valid (anymore?), and --masterport 
should be used instead.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to