Hi Stefan,
Not in my book it shouldn't go away. It is the only place I can get good
debug info on perl scripts ... OK, not the only place but it is easiest
place to find the needed info. Since perl is not 100% dead and gone,
please keep it. It seems fine as-is, as I've been using it 10 years
On Sep 25, 2010, at 8:08 PM, Stefan Fritsch wrote:
On Sunday 26 September 2010, Rich Bowen wrote:
Another question on this thread - is ScriptLog also going away?
It hasn't been on my radar so far. Should it?
pros:
- per dir config instead of per vhost
- possibly finer control with different
On Sat, Sep 06, 2003 at 08:19:39AM -0700, Ian Holsman wrote:
> I guess the other one I'd like to see is rewritelogging/loglevel from
> inside a .htaccess file.
> It's a real bitch trying to debug rewrite rules inside this (and in
> rules inside of directory/location blocks)
The worst thing about
r bad (you could force a CGI bomb to be a status
200 or a status 500, output an error page, etc.).
-Original Message-
From: Manoj Kasichainula [mailto:[EMAIL PROTECTED]
Sent: Monday, September 08, 2003 3:08 AM
To: [EMAIL PROTECTED]
Subject: Re: ScriptLog
On Sun, Sep 07, 2003 at 05:38
On Sun, Sep 07, 2003 at 05:38:56PM -0400, Cliff Woolley wrote:
> On Sun, 7 Sep 2003, Manoj Kasichainula wrote:
>
> > If it's only for debugging, can't CGI writers just add a line to their
> > code to rebind stderr to a file?
>
> Only if the error is output from the script as opposed to a compilat
On Sun, 7 Sep 2003, Manoj Kasichainula wrote:
> If it's only for debugging, can't CGI writers just add a line to their
> code to rebind stderr to a file?
Only if the error is output from the script as opposed to a compilation
failure or other interpreter weirdness.
On Sat, Sep 06, 2003 at 04:57:25PM -0400, Cliff Woolley wrote:
> On Sat, 6 Sep 2003, Astrid Keßler wrote:
>
> > +1 for ScriptLog and RewriteLog(Level), although I'm not sure this is
> > easy to implement. As I know, all log files are opend at server start.
> > Allow directory based logging would m
* Glenn wrote:
> On Sat, Sep 06, 2003 at 02:38:34PM +0200, Andr? Malo wrote:
>> * Cliff Woolley wrote:
>>
>>> It's too bad you can't set the ScriptLog in a per-dir context -- that
>>> would allow an individual user (aka myself) to debug their own cgi scripts
>>> into their own error log even thoug
On Sat, Sep 06, 2003 at 02:38:34PM +0200, Andr? Malo wrote:
> * Cliff Woolley wrote:
>
> > It's too bad you can't set the ScriptLog in a per-dir context -- that
> > would allow an individual user (aka myself) to debug their own cgi scripts
> > into their own error log even though there's no global
Erik wrote.
> On 06/09/2003, at 11:43, Astrid Keßler wrote:
>> Cliff wrote:
>>
>>> Yes, it would. But for a debug log it's a price I'm willing to
>>> accept.
>>
>> Just an unformed idea: allow these directives within (and
>> ?), but not within .htaccess files. The log file could be
>> opened as
* Ian Holsman ([EMAIL PROTECTED]) wrote :
> Cliff Woolley wrote:
> >It's too bad you can't set the ScriptLog in a per-dir context -- that
> >would allow an individual user (aka myself) to debug their own cgi scripts
> >into their own error log even though there's no global ScriptLog enabled.
> >
>
On Sun, 7 Sep 2003, Erik Abele wrote:
> Hmm, yeah, but this won't help with the problem Cliff is facing, I
> guess: he is probably logged into apache.org and wants to debug a
> script he's developing right now, so (pre-)enabling it in the server
> config makes no sense. It'd be really nice to have
Astrid Keßler wrote:
Cliff wrote:
On Sat, 6 Sep 2003, Astrid Keßler wrote:
+1 for ScriptLog and RewriteLog(Level), although I'm not sure this is
easy to implement. As I know, all log files are opend at server start.
Allow directory based logging would mean to open and close log files per
reque
On 06/09/2003, at 11:43, Astrid Keßler wrote:
Cliff wrote:
Yes, it would. But for a debug log it's a price I'm willing to
accept.
Just an unformed idea: allow these directives within (and
?), but not within .htaccess files. The log file could be
opened as usual.
Hmm, yeah, but this won't help
Cliff wrote:
> On Sat, 6 Sep 2003, Astrid Keßler wrote:
>> +1 for ScriptLog and RewriteLog(Level), although I'm not sure this is
>> easy to implement. As I know, all log files are opend at server start.
>> Allow directory based logging would mean to open and close log files per
>> request.
> Yes
On Sat, 6 Sep 2003, Astrid Keßler wrote:
> +1 for ScriptLog and RewriteLog(Level), although I'm not sure this is
> easy to implement. As I know, all log files are opend at server start.
> Allow directory based logging would mean to open and close log files per
> request.
Yes, it would. But for a
> I guess the other one I'd like to see is rewritelogging/loglevel from
> inside a .htaccess file.
> It's a real bitch trying to debug rewrite rules inside this (and in
> rules inside of directory/location blocks)
+1 for ScriptLog and RewriteLog(Level), although I'm not sure this is
easy to implem
Cliff Woolley wrote:
It's too bad you can't set the ScriptLog in a per-dir context -- that
would allow an individual user (aka myself) to debug their own cgi scripts
into their own error log even though there's no global ScriptLog enabled.
--Cliff
Hey Cliff,
I guess the other one I'd like to see i
* Cliff Woolley wrote:
> It's too bad you can't set the ScriptLog in a per-dir context -- that
> would allow an individual user (aka myself) to debug their own cgi scripts
> into their own error log even though there's no global ScriptLog enabled.
+1 for per-dir with AllowOverride Options.
nd
19 matches
Mail list logo
