On Tue, Feb 17, 2009 at 1:35 AM, Francis J. Lacoste
<email address hidden> wrote:
> There is such a default and it's 'development'.
>
> I don't understand the problem here.
The problem is that the default of 'development' is only appropriate
on developer boxes. The default on other servers needs to be set in
the shell startup scripts for interactive use, in the crontab for
batch job use, and now via wrappers for processes spawned by processes
running as other users, such as apache.
If nothing else, it will make our production and staging environments
cleaner because the LPCONFIG environment variable will only ever need
to be specified to override the default for that server.
On Tue, Feb 17, 2009 at 1:35 AM, Francis J. Lacoste
<email address hidden> wrote:
> There is such a default and it's 'development'.
>
> I don't understand the problem here.
The problem is that the default of 'development' is only appropriate
on developer boxes. The default on other servers needs to be set in
the shell startup scripts for interactive use, in the crontab for
batch job use, and now via wrappers for processes spawned by processes
running as other users, such as apache.
If nothing else, it will make our production and staging environments
cleaner because the LPCONFIG environment variable will only ever need
to be specified to override the default for that server.