>>> On 4/11/2008 at 5:17 PM, in message
<[EMAIL PROTECTED]>, "Bernard Li"
<[EMAIL PROTECTED]> wrote:
> On Fri, Apr 11, 2008 at 4:09 PM, Jesse Becker <[EMAIL PROTECTED]> wrote:
>
>> If there is an existing /etc/gmond.conf, then create a new "patched"
>> file as something like /etc/gmond.conf.upgr
On Fri, Apr 11, 2008 at 4:09 PM, Jesse Becker <[EMAIL PROTECTED]> wrote:
> If there is an existing /etc/gmond.conf, then create a new "patched"
> file as something like /etc/gmond.conf.upgrade_from_3.0.x. This
> leaves the existing file alone, reducing the risk of breaking
> something. Also,
On Fri, Apr 11, 2008 at 7:03 PM, Bernard Li <[EMAIL PROTECTED]> wrote:
> Right now I am working on the upgrade path from 3.0.x to 3.1.x. Since
> there are diffs between 3.0.x gmond and 3.1.x gmond, I am proposing
> the following changes in the spec file during upgrade:
>
> %postun
> gmond -t
Hi all:
Right now I am working on the upgrade path from 3.0.x to 3.1.x. Since
there are diffs between 3.0.x gmond and 3.1.x gmond, I am proposing
the following changes in the spec file during upgrade:
%postun
gmond -t > /tmp/gmond.conf.old /* generate default conf from 3.0.x */
%post
gmond -t >
