Hello,

Sonic wrote:

Hi!

Yes, the problem lies in apacheupdate.pl, it has the wrong values hardcoded in it, but I don't know why it is executed. It is not in crontab and not in repligard_staging_to_live.sh....

Right, which Aegir version you're running? Maybe it executes the script when necessary... Quick 'n dirty: rename the apacheupdate.pl. :)

Cheers!

  //Henri

Bye,

A.f.

Am Donnerstag, 10. Juni 2004 14:44 schrieb Henri Kaukola:

Hello,

Aegir should not do this by default. Are you
running some of the scripts that are provided
with Aegir package?

Some like staging_to_live.sh, apacheupdate.pl etc.

If you have any of those in your crontab,
you should probably remove the apacheupdate.pl.

I'm not very familiar with the Aegir scripts but
the apacheupdate.pl sounds like the source of
your problem.

Cheers!

  //Henri

Sonic wrote:
> Hi!
>
> I noticed that when I create a new company and a website in Aegir, it
> automatically updates midgard-data.conf for me. the problem is that

in the

> process some settings get changed and MidgardRootFile and CustomLog

are set

> to wrong values  (MidgardRootFile is set to

/usr/lib/apache/midgard-root.php,

> but should be /usr/lib/apache/1.3/midgard-root.php on Debian), so

that the

> server will stop working after a restart.
> Is this a configuration problem or a bug in Aegir. If its a bug,

should I

> report it at tigris.org (the bug tracking system doesn't look like

anybody

> uses it)?
>
> Bye,
>
> A.f.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to