Jesse,
Perhaps you should take a fresh approach. Restate your original goal that
started all your template efforts. Perhaps someone else has another way
to do it.
Sincerely,
--
Neil Watson
416-673-3465
CONFIDENTIALITY WARNING
This communication, including any attachments, is for the exclus
Message-
>From: Jesse Becker [mailto:becker...@mail.nih.gov]
>Sent: Friday, March 05, 2010 12:57 PM
>To: nwat...@symcor.com
>Cc: Becker, Jesse (NIH/NHGRI) [C]; help-cfengine@cfengine.org;
>help-cfengine-boun...@cfengine.org; Justin Lloyd
>Subject: Re: Thoughts about copy_fro
Message-
From: Jesse Becker [mailto:becker...@mail.nih.gov]
Sent: Friday, March 05, 2010 12:57 PM
To: nwat...@symcor.com
Cc: Becker, Jesse (NIH/NHGRI) [C]; help-cfengine@cfengine.org;
help-cfengine-boun...@cfengine.org; Justin Lloyd
Subject: Re: Thoughts about copy_from
On Fri, Mar 05, 2010
On Fri, Mar 05, 2010 at 02:45:19PM -0500, nwat...@symcor.com wrote:
>help-cfengine-boun...@cfengine.org wrote on 2010-03-05 14:37:57:
>> I'd like to add one more suggestion as well:
>>
>> * Include the ability to call expand_scalars in the same promise as
>> copying a file from a remote host.
help-cfengine-boun...@cfengine.org wrote on 2010-03-05 14:37:57:
> I'd like to add one more suggestion as well:
>
> * Include the ability to call expand_scalars in the same promise as
> copying a file from a remote host. Currently, this has to be done
via
> two separate promises: one to
On Fri, Mar 05, 2010 at 02:11:42PM -0500, Justin Lloyd wrote:
>I just wanted to throw out a couple of thoughts about copy_from that
>have come up in my mind during my policy development:
Agreed on all three points.
I'd like to add one more suggestion as well:
* Include the abil
I just wanted to throw out a couple of thoughts about copy_from that
have come up in my mind during my policy development:
* The reference manual doesn't specify the default value for copy_from's
copy_backup attribute. (That goes for a number of things in the
documentation
