search for: snowmobile

I know someone completed this but I''m not sure the hows and whats of it. Can someone put up a doc or email about this?

Quoting asterisk-users-request@lists.digium.com: > > Would it be considered trolling to start a thread on Cleaning Maple > > Syrup off of Dial Pads, or Wiring your Moose for Wi-Fi? > > Let's not forget the weekly "tooques and telephony" segment, and a > review of > the best block heaters for your wi-fi fones. > Oh, we're gonna have a good time next

Hello, I've been asked to test this, can anyone help me? The platform I would like to test on: - Lenny/amd64 - Intel VT-i (Xen HVM support) I've looked over the various threads and wiki pages on the issue and I thought I would try to summarise it more concisely: dom0 (32 bit): - regular install using Lenny CD, Debian Installer, i386 - install the kernel package from etch,

Hi puppet masters, while working on my site I came across a requirement that might be helpful for others as well.... With the aim of confining human errors as much as possible, I thought that it would be nice to have yum repositories disabled so that specific repositories could be enabled for certain packages. This is easily implementable via command-line, but I found that the

Has the component/type defaults syntax changed for 0.22.x? I have a component: <snip> define remotefile($owner=root, $group=root, $mode, $source, $backup=false, $recurse=false, $groupname="default") { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

Hi, I just upgraded to puppet 0.20.0 today after a short time playing with 0.19.3. The docs say to use the uppercase form for types but that seems to break for me. When I updated the remotefile function to use the new way, the puppet clients complain about objects not being found. For example: ----- OLD WAY (works, just with deprecations) ----- define remotefile (...) { file { $name :

Has anyone done rollbacks with puppet? The story goes that last night I pushed a change out, which intentionally changed the way certain services where managed. The change involved pushing out a few files, cronjobs, etc., which was okay until it was discovered there was a bug with the service. My configurations are kept in subversion and rolling back to a previous configuration would have

I testing Puppet 0.19.3. If we decide to use it, we''d deploy it across several thousand hosts. The method described for creating client certificates described in the documentation - running "puppetd --server <server> --waitforcert 60 --test" and "puppetca --sign <client>" - is not practical for our installation. I''ve tried creating

Hello everyone, A long time ago, I posted the Stanford Best Practices and I''ve gone through and updated it today. I''d like to have people go through it and see if we can strip out some Stanford specific stuff and tag this as an official best practice. I think an official best practice will be important as more and more people consider making shareable modules, etc (mostly