On Mar 28, 8:47 pm, deet <somew...@gmail.com> wrote: > I like the idea of accessing this information through facter instead > of needlessly running ifconfig again.
Indeed. Take a look at the facter libraries, they're quite readable overall. Plenty of good bits in 'facter/util' that you can use also. > Is their any "standard" location to put a config.yml file like in > your above example? Or just where ever I happen to store config files > at my location? I think i'll extend your example for default gateway > lookups. I think /usr/local/etc/ is pretty standard for configs that aren't supplied by the base os. If they're specific to a single program you could also see "/usr/local/$program/". Check 'man hier' of your platform of choice for more info. In my case we're using config.yml to store all those site common settings that usually get embedded into 10 different scripts and then forgotten. Ive done similar facts for providing gateway & broadcast addresses based on existing facts. Those were used for dhcp servers to automagically build dhcp.conf settings for attached networks. Let me know if you have any questions. -- 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.
