launchpad-dev team mailing list archive

[Ian Booth <ian.booth@xxxxxxxxxxxxx>]

Hi Tom

On 02/11/10 19:18, Tom Haddon wrote:
> On Tue, 2010-11-02 at 13:00 +1000, Ian Booth wrote:
>> Hi people
>>
>> I currently have a mp for review which moves the various launchpad log
>> and trace files from the root directory to a logs subdir directly off
>> the root directory. However, I need input from people as to what impact
>> this may have on production systems, namely cleanup scripts or metrics
>> gathering tools and the like.
> 
> Do you mean the root directory of the code tree? 
>

Yes. On a development system, the log files are placed in the root
directory of the working tree for the particular branch.

>>
>> The affected log files include:
>>
>> The affected log files include only those associated with Launchpad itself:
>> - thread*.request
>> - launchpad.log
>> - launchpad-access.log
>> - trace.log
>> - pagetests-access.log
>> - google-stub.log
> 
> Of these, the only ones I see in the production systems in the code tree
> itself is the thread*.request files. I don't see the last two at all
> (maybe those aren't actually created on production?) but the others are
> all sent to log directories per configs defined in
> lp-production-configs. We'd like that part to stay that way, but have no
> objection to moving the thread*.request files as well.
>

I've modified the necessary configs to affect the behaviour of the
system when run under development. It doesn't surprise me that not all
of the log/trace files created on a development system are present in
production. If the prod deployments have their own configs to control
where the various log files go, then I think everything will be ok with
my changes to devel. :-) I've not got enough knowledge to know for sure,
hence the question. I think you are suggesting we will be ok.

Thanks for the input.