Second vote for "ack", it is awesome for "grepping" through source code trees. Details here: http://betterthangrep.com/ (Note that it is available as an OS packages for many OSes/distros).
-Brian On Mon, Feb 28, 2011 at 10:34 PM, Brian Gallew <g...@gallew.org> wrote: > Doug, there's a command-line tool called "ack" which is an enhanced grep > replacement. It will probably do what you wat with finding your nodes. > > On Mon, Feb 28, 2011 at 4:43 PM, Douglas Garstang <doug.garst...@gmail.com> > wrote: >> >> >> On Mon, Feb 28, 2011 at 1:17 PM, Alan Barrett <a...@cequrux.com> wrote: >>> >>> On Mon, 28 Feb 2011, Douglas Garstang wrote: >>>>> >>>>> How is it possible to use external nodes as local files? I was under >>>>> the impression that node_terminus=exec or node_terminus=ldap were the only >>>>> ways of using external nodes. >>>> >>>> Really? That might be because everyone seems to be on the LDAP external >>>> node bandwagon. You can put a "external_nodes = <script>" in your >>>> puppet.conf file, where <script> is a script that does whatever it needs to >>>> read the local files and dump the output in YAML format. >>> >>> Oh, so you are using an external node classifier script in the usual way, >>> with node_terminus = exec; you are just using unusual terminology to >>> describe it. Puppet knows nothing about "external nodes as local files"; >>> all it knows is that you have an external node classifier script. >>> >> >> I felt I had to explicitly say I was using files, since it was relevant to >> the understanding of my problem, and I seem to be about the only person who >> uses files, as I need to revision control them. >> >>> >>> The question about where to put the data files used by your script still >>> stands, of course, and I would still probably put them under an >>> environment-specific directory. >>> >>>> Yeah, but then you have the problem of not knowing what environment the >>>> node is in, and you have to go digging around for it. The more environments >>>> you have, the more places you have to dig. >>> >>> I have an external node classifier script whose sole task is to go >>> digging in multiple environment-specific directories to figure out which >>> environment a client node belongs to. >> >> Yes, but I, as a human, have to do digging through the directories too, to >> find where to edit the file. I guess I could write a script that does the >> searching and returns the full path to the file. That would save some time. >> >> Doug >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@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. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@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. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
