Issue #2699 has been updated by Matthias Saou.
Todd Zullinger wrote: > Right, but puppetd takes a --port option to specify the port it listens on as > well as --masterport for the port to connect to. Well, last I tried, the --port option wasn't valid for the client, so the sysconfig/initscript option is currently "broken" and switching to use --masterport fixes it. Or are you implying that the puppet _client_ listens on a tcp port for connections? (if it doer or even can, then I'm highly confused) ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
