bug-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cfservd under load - db crash, MaxConnections


From: Mark . Burgess
Subject: Re: cfservd under load - db crash, MaxConnections
Date: Thu, 9 Dec 2004 08:08:07 +0100 (MET)

I would like to understand better why the -Q thing affects
spalytime. It applies only to cfexecd *before* any real cfengine
runs

M

On  8 Dec, Eric Sorenson wrote:
> On Wed, 8 Dec 2004 address@hidden wrote:
> 
>>
>> Thank you!
> 
> Mark, I need a little help to know the right way to fix this. 
> I think that -Q ought to set PARSEONLY, but currently the call
> to QueryCheck() happens after the PARSEONLY exits (cfagent.c:166).
> 
> I think it is safest to move that test a little later (see attached)
> instead of moving the QueryCheck() to be earlier, but I do not know
> if the result of running CfOpenLog, CheckSystemVariables will conflict
> with another intended purpose of PARSEONLY.  What do you think?
> 
> --- cfengine-2.1.11/src/cfagent.c       2004-10-26 00:44:31.000000000 -0700
> +++ cfengine-2.1.11-eric/src/cfagent.c  2004-12-08 15:06:04.000000000 -0800
> @@ -163,18 +163,18 @@
>       exit(1);
>       }
> 
> - if (PARSEONLY)                            /* Establish lock for root */
> -    {
> -    exit(0);
> -    } 
> -
>    CfOpenLog();
>    CheckSystemVariables();
> 
>    SetReferenceTime(false); /* Reset */
> 
>    QueryCheck();
> - 
> +
> + if (PARSEONLY)                            /* Establish lock for root */
> +    {
> +    exit(0);
> +    } 
> +
>    DoTree(2,"Main Tree");
>    DoAlerts();
> 
> @@ -1734,6 +1734,7 @@
>                }
> 
>             IGNORELOCK = true;
> +          PARSEONLY = true;
>             NOSPLAY = true;
>             QUERYVARS = SplitStringAsItemList(optarg,',');
>             break;
> 
> 
> 



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  address@hidden
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





reply via email to

[Prev in Thread] Current Thread [Next in Thread]