On 22/09/2012, at 4:23 PM, jdehnert wrote:
>
>
> On Friday, September 21, 2012 7:11:18 PM UTC-7, Jakov Sosic wrote:
> On 09/22/2012 03:21 AM, jdehnert wrote:
>
> > I'm aware of the issues of installing software through source vs. pkg
> > management systems. I should have mentioned that I've
Le 21 sept. 2012 à 17:05, jcbollinger a écrit :
>
>
> On Friday, September 21, 2012 4:35:41 AM UTC-5, Fabrice Bacchella wrote:
> I'm starting it by hand. It's the same process (pid 1845) that is nulling
> stderr that is writing to it, so it's not related to the way it's launched,
> --debug pr
Le 21 sept. 2012 à 15:35, jcbollinger a écrit :
>
>
> On Friday, September 21, 2012 6:21:04 AM UTC-5, Fabrice Bacchella wrote:
> When puppet is launched as a daemon, a kill -USR trigger a catalog run :
>
> Sep 21 12:56:01 XXX puppet-agent[15324]: Caught USR1; calling reload
> Sep 21 12:56:24
On Fri, Sep 21, 2012 at 6:48 PM, Jakov Sosic wrote:
> On 09/19/2012 11:55 PM, Hai Tao wrote:
>>
>> There seems to be a few vmware tools installation modules. Has someone
>> used these modules to install VMware tools?
>>
>> Searching http://forge.puppetlabs.com ...
>> NAMEDESCRI
Possibly stupid question - how do I know when I have to use a variable
in a string like this - "${apache::params::moddir}/php.conf" - or when
it's safe to just do it like this -
"$apache::params::moddir/php.conf". It seems like sometimes I need to
do the former, and other times the latter.
I don't
It turns out that you do always need the {}, and this just works because
the / in the path breaks the variable-finding regex.
Thanks to rodjek on irc! :-D
On Saturday, September 22, 2012 3:15:07 PM UTC-4, Zachary Alex Stern wrote:
>
> Possibly stupid question - how do I know when I have to use a
It is a useful tool. However, the difficulty is that our ENV has
multiple versions of ESX hosts, 3.5, 4.1 and 5.0. The guest OS has no
clue what version of ESX it is running on, so how can puppet server
push a correct version of vmware tools to a client?
On Sat, Sep 22, 2012 at 11:20 AM, Michael S
I believe the open-vm-tools at http://packages.vmware.com/tools are ESX
host version agnostic.
We pull the rhel 4-6 repos into RHN satellite and just use puppet ensure
the latest is installed.
If you do t use satellite you could just clone the repo and configure yum
on the clients.
Packages are
I've done something similar using the open-vm package on debian hosts.
On Saturday, September 22, 2012 3:06:10 PM UTC-5, Alan Evans wrote:
>
> I believe the open-vm-tools at http://packages.vmware.com/tools are ESX
> host version agnostic.
>
> We pull the rhel 4-6 repos into RHN satellite and
hi
please delete the common information from the key value ,may be you used
ssh-keygen -t rsa -C "XXX".
2012/9/21 Hiu
> hi Admin,
>
> How are you?
>
> I have a easy ssh_authorized_key like below
>
>ssh_authorized_key { "hiu@$fqdn":
> name => "hiu@$fqdn",
>
I think vmware tools RPMs are categarized by ESX version, am I wrong?
On Sat, Sep 22, 2012 at 7:42 PM, Christian McHugh
wrote:
> I've done something similar using the open-vm package on debian hosts.
>
>
>
> On Saturday, September 22, 2012 3:06:10 PM UTC-5, Alan Evans wrote:
>>
>> I believe the
11 matches
Mail list logo
