search for: pounsett

...extension, and I'm trying to figure out how to get back to the top of the context and have asterisk wait for a new extension to dial. I've dug through the Asterisk O'Reilly book, and googled around some, but haven't come up with the answer. Thoughts anyone? Thanks, Matt Pounsett -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) iEYEARECAAYFAknqDAgACgkQmFeRJ0tjIxEjtACfVujjF+WC/If7LubuY1mfU8og 4N8An3tAXOQFpQDALqPpuDVWhOPP7ETf =RwS5 -----END PGP SIGNATURE-----

I''m trying to extend the standard ''user'' type to add maintenance of some of the contents of a user''s home directory, and I''m trying to avoid creating an entirely new custom type if I can. The approach I''m taking is to create a site::user defined type which in turns calls the standard user type. I''m having a problem figuring out

Hello puppet world, I''m sure this is probably an easy fix, but I cannot seem to resolve this issue. The puppetmaster starts correctly and so does the puppet agent, which receives the update correctly if I restart the puppet agent service manually or during the timed updates; however, if I perform an "puppet kick", it just fails with the following error: Triggering

I''m having an issue with the default puppet.conf distributed with puppet 2.6.4 (FreeBSD port). I''ve reproduced the problem with a completely fresh install on a completely fresh OS in a VM. Under these conditions, running puppetmaster with no config is fine, but simply moving the puppet.conf-dist file to puppet.conf causes the following errors on console: Performing sanity

I have one module, kibana, that defines a file snippet for the apache module to fulfill (e.g., /etc/https/conf.d/kibana.conf). The apache::params class defines a variable of the path of where this snippet should be placed, $config_d. The snippet uses this variable in its definition. However, it seems that the snippet never resolves the $apache::params::config_d variable, and I''m