On Jun 3, 2010, at 3:05 PM, Christopher Johnston wrote: > You know what the problem was, my ordering. I had app_tcp first and not port > 1002 so thats likely why it was not getting picked up. Worked, but hit > another snag. Now try adding another app name, same port but for udp, it > will just get overwritten.
I addressed both of those things in my initial reply. On the order of `set` statements: > Setting the “name” doesn't seem to work until after the thing exists, which > is why it appears second on the list. On adding both TCP and UDP entries: > So, if you can find something that makes an item unique, you can use that to > specify a path. If two entries are using the same port number, that obviously won't work as a unique identifier. You could maybe use a unique comment on each one, but there seems to be that bug where no space appears between protocol and comment. Perhaps there's a way to specify a path using more than one component. A combination of port and protocol should be unique, for example. -- Rob McBroom <http://www.skurfer.com/> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
