Issue #2699 has been updated by Todd Zullinger.
Right, but puppetd takes a --port option to specify the port it listens on as well as --masterport for the port to connect to. I understand that the comment and default of 8140 make it seem like it should refer to the master port, but the history in git makes it unclear to me which it is really intended to be used with. I'd like to get that cleared up so we don't just change it to --masterport and then get an immediate bug report from someone that used the value to control the --port option. I understand that we're talking about the client init/sysconfig here and that the puppetmaster service has it's own init/sysconfig. ---------------------------------------- Bug #2699: Configurable port in the included Red Hat init script is broken http://projects.reductivelabs.com/issues/2699 Author: Matthias Saou Status: Needs design decision Priority: Normal Assigned to: Todd Zullinger Category: Red Hat Target version: 0.25.1 Affected version: 0.25.1rc1 Keywords: Branch: 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 -~----------~----~----~----~------~----~------~--~---
