On 6 August 2010 00:35, Rein Henrichs r...@puppetlabs.com wrote:
* Per #4466, Ruby has trouble reading files in /proc [1]. The
alternative is to use `bin/cat`.
* Also refactored methods to explicitly redirect standard error to
/dev/null for *nix and BSD system calls.
+1
Random thought for
On 6 August 2010 00:35, Rein Henrichs r...@puppetlabs.com wrote:
From: Rein Henrichs re...@reinh.com
Rewrite of uptime facts and supporting utility methods. Works on unix,
BSD, windows. No longer makes redundant system calls.
+1, tested locally
Uses Facter::Util::Uptime utility methods:
*
This is a hairy problem to tackle, as I recently tried. The biggest
problem is that in the Etc module there seems to be no function for
setting group members. Therefore, this resource parameter would have to
be enforced by directly manipulating /etc/group. That's not very
puppet-like so I am
On Fri, Aug 6, 2010 at 2:23 AM, Paul Nasrat pnas...@gmail.com wrote:
Random thought for 1.6 or later we could have a ProcFile and Sysctl
specific class (and dmidecode) to encapsulate the complexities of
different platforms/versions so it's easy to do stuff and provides a
handy way to prevent
On 6 August 2010 17:55, Paul Berry p...@puppetlabs.com wrote:
On Fri, Aug 6, 2010 at 2:23 AM, Paul Nasrat pnas...@gmail.com wrote:
Random thought for 1.6 or later we could have a ProcFile and Sysctl
specific class (and dmidecode) to encapsulate the complexities of
different platforms/versions
Excerpts from Paul Berry's message of Fri Aug 06 09:55:37 -0700 2010:
On Fri, Aug 6, 2010 at 2:23 AM, Paul Nasrat pnas...@gmail.com wrote:
Random thought for 1.6 or later we could have a ProcFile and Sysctl
specific class (and dmidecode) to encapsulate the complexities of
different
- Rein Henrichs r...@puppetlabs.com wrote:
Excerpts from Paul Berry's message of Fri Aug 06 09:55:37 -0700 2010:
On Fri, Aug 6, 2010 at 2:23 AM, Paul Nasrat pnas...@gmail.com
wrote:
Random thought for 1.6 or later we could have a ProcFile and Sysctl
specific class (and
On Aug 6, 2010, at 9:39 AM, Joe McDonagh wrote:
This is a hairy problem to tackle, as I recently tried. The biggest
problem is that in the Etc module there seems to be no function for
setting group members. Therefore, this resource parameter would have
to be enforced by directly
On 08/06/2010 01:17 PM, Luke Kanies wrote:
On Aug 6, 2010, at 9:39 AM, Joe McDonagh wrote:
This is a hairy problem to tackle, as I recently tried. The biggest
problem is that in the Etc module there seems to be no function for
setting group members. Therefore, this resource parameter would
On 08/06/2010 01:28 PM, Luke Kanies wrote:
On Aug 6, 2010, at 10:21 AM, Joe McDonagh wrote:
On 08/06/2010 01:17 PM, Luke Kanies wrote:
On Aug 6, 2010, at 9:39 AM, Joe McDonagh wrote:
This is a hairy problem to tackle, as I recently tried. The biggest
problem is that in the Etc module there
On Aug 6, 2010, at 10:53 AM, Joe McDonagh wrote:
On 08/06/2010 01:28 PM, Luke Kanies wrote:
On Aug 6, 2010, at 10:21 AM, Joe McDonagh wrote:
On 08/06/2010 01:17 PM, Luke Kanies wrote:
On Aug 6, 2010, at 9:39 AM, Joe McDonagh wrote:
This is a hairy problem to tackle, as I recently tried.
+1 or, as they used to say on AOL, Me Too!
On Fri, Aug 6, 2010 at 10:12 AM, R.I.Pienaar r...@devco.net wrote:
- Rein Henrichs r...@puppetlabs.com wrote:
Excerpts from Paul Berry's message of Fri Aug 06 09:55:37 -0700 2010:
On Fri, Aug 6, 2010 at 2:23 AM, Paul Nasrat pnas...@gmail.com
Hi,
Does anybody know how I can set a user's password with puppet without
knowing what the hash will be? There is code I've tried from here:
http://groups.google.com/group/puppet-users/browse_thread/thread/fa919b524c4a9323
But it does not seem to work, I think because the way the hash is set
on
13 matches
Mail list logo
