Issue #2699 has been updated by Todd Zullinger.
You can run puppetd --port 1234. The puppetd executable from 0.25.1rc1 still supports this (as in, it doesn't complain about it). I don't have much time to fully test it right now, but I expect it to still work. The idea with this is that you can use puppetrun from the puppetmaster to to trigger a puppet run on the clients. So yeah, the client can listen on a TCP port for connections and this port is specified via the --port option. In that case, it seems like we should have a way to configure both the port puppetd listens on as well as the port it connects to the puppetmaster on in the client's sysconfig file. ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
