Re: mod_auth-any/3362: Password File is not parsed correctly

1998-11-08 Thread marc
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]


Synopsis: Password File is not parsed correctly

State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Sat Nov  7 17:14:21 PST 1998
State-Changed-Why:
What part of check to be sure the bug is in the current version
don't you understand?

It is not a bug, since the htpasswd file was defined to be
user:passwd, with no mention of any other :s in there or
allowing any other data.  This was changed in 1.3a1 to allow
for extra : seperated info at the end.

Please, it is a waste of everyone's time if you don't follow
instructions and insist on submitting bug reports for year
old programs.



Re: os-linux/3345: Apache compiled but did not start (shared modules)

1998-11-08 Thread marc
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]


Synopsis: Apache compiled but did not start (shared modules)

State-Changed-From-To: feedback-closed
State-Changed-By: marc
State-Changed-When: Sun Nov  8 00:06:46 PST 1998
State-Changed-Why:
User reports problem solved.



Re: os-windows/3359: Configuring Apache only for proxy cache it report a runtime error.

1998-11-08 Thread Marc Slemko
The following reply was made to PR os-windows/3359; it has been noted by GNATS.

From: Marc Slemko [EMAIL PROTECTED]
To: Francesco Garganese [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: os-windows/3359: Configuring Apache only for proxy cache it
 report a runtime error.
Date: Sun, 8 Nov 1998 00:04:25 -0800 (PST)

 On 6 Nov 1998, Francesco Garganese wrote:
 
  
  Number: 3359
  Category:   os-windows
  Synopsis:   Configuring Apache only for proxy cache it report a runtime 
  error.
  Confidential:   no
  Severity:   serious
  Priority:   medium
  Responsible:apache
  State:  open
  Class:  sw-bug
  Submitter-Id:   apache
  Arrival-Date:   Fri Nov  6 15:10:01 PST 1998
  Last-Modified:
  Originator: [EMAIL PROTECTED]
  Organization:
  apache
  Release:1.3.3
  Environment:
  WinNT 4.0 Service Pack 3
  The binary distribution downloaded at apache/dist/binaries/win32/
  Description:
  Doctor Watson reports a runtime problem at 
  The event viewer report many times the following error:
  The application, , generated an application error The error occurred on 11/ 
  6/1998 @ 22:35:30.621 The exception generated was c005 at address 
  00be7a0e (nosymbols)
  
 
 How exactly are you trying to configure it?
 
 What exactly did you change in the configuration files?
 
 Is there anything in the error log?
 


Re: os-linux/3345: Apache compiled but did not start (shared modules) (fwd)

1998-11-08 Thread Marc Slemko
The following reply was made to PR os-linux/3345; it has been noted by GNATS.

From: Marc Slemko [EMAIL PROTECTED]
To: Apache bugs database [EMAIL PROTECTED]
Cc:  Subject: Re: os-linux/3345: Apache compiled but did not start (shared 
modules)
 (fwd)
Date: Sun, 8 Nov 1998 00:02:57 -0800 (PST)

 -- Forwarded message --
 Date: Sun, 8 Nov 1998 03:09:16 +0100 (MET)
 From: Sven Anders [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Re: os-linux/3345: Apache compiled but did not start (shared modules)
 
 
 On 5 Nov 1998 [EMAIL PROTECTED] wrote:
 
  Synopsis: Apache compiled but did not start (shared modules)
  
  State-Changed-From-To: open-feedback
  State-Changed-By: lars
  State-Changed-When: Thu Nov  5 15:10:09 PST 1998
  State-Changed-Why:
  
  I'm not able to reproduce this problem on a
  Linux system with glibc 2.0.7, but I tested
  with gcc.
  
  Please check your compiler installation.
  
  Severity-Changed-From-To: serious-non-critical
  Severity-Changed-By: lars
  Severity-Changed-When: Thu Nov  5 15:10:09 PST 1998
 
 The gcc was ok.
 It was the glibc. glibc-2.0.6 did NOT work !
 I updated to 2.0.7 and now all runs smoothly! :-)
 
 Thanks for all!
 
 Greetings
  Sven
 
 -- 
  I am the embodiment of modern medicine.  Der Dativ ist dem 
  The holographic doctor, USS-Voyager  Genitiv sein Tod. 
 
  
  http://www.fmi.uni-passau.de/~anderss  email: [EMAIL PROTECTED] 
 
 


Re: os-linux/3343: Server dies after 1-20 hours of usage.

1998-11-08 Thread Marc Slemko
On 6 Nov 1998, Mark wrote:

 The following reply was made to PR os-linux/3343; it has been noted by GNATS.
 
 From: Mark [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Re: os-linux/3343: Server dies after 1-20 hours of usage.
 Date: Fri, 06 Nov 1998 21:36:06 +
 
  [EMAIL PROTECTED] wrote:
  
   [In order for any reply to be added to the PR database, ]
   [you need to include [EMAIL PROTECTED] in the Cc line ]
   [and leave the subject line UNCHANGED.  This is not done]
   [automatically because of the potential for mail loops. ]
   [If you do not include this Cc, your reply may be ig-   ]
   [nored unless you are responding to an explicit request ]
   [from a developer.  ]
   [Reply only with text; DO NOT SEND ATTACHMENTS! ]
  
   Synopsis: Server dies after 1-20 hours of usage.
  
   Comment-Added-By: lars
   Comment-Added-When: Fri Nov  6 10:26:46 PST 1998
   Comment-Added:
  
   Are you using NFS?
   Any third party modules?
  
  No.  NFS is disabled, and we did not compile any 3rd party modules into
  the server.  The only extra module that I enabled was the status
  module.  The server ran fine for about 6 months before this started.  Is
  there anything in the OS itself that may have changed to cause this
  problem?

Did you upgrade your kernel version or any libraries, especially libc
around when it started happening?




Re: os-linux/3343: Server dies after 1-20 hours of usage.

1998-11-08 Thread Marc Slemko
The following reply was made to PR os-linux/3343; it has been noted by GNATS.

From: Marc Slemko [EMAIL PROTECTED]
To: Mark [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: os-linux/3343: Server dies after 1-20 hours of usage.
Date: Sun, 8 Nov 1998 00:06:06 -0800 (PST)

 On 6 Nov 1998, Mark wrote:
 
  The following reply was made to PR os-linux/3343; it has been noted by GNATS.
  
  From: Mark [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Cc: [EMAIL PROTECTED]
  Subject: Re: os-linux/3343: Server dies after 1-20 hours of usage.
  Date: Fri, 06 Nov 1998 21:36:06 +
  
   [EMAIL PROTECTED] wrote:
   
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]
   
Synopsis: Server dies after 1-20 hours of usage.
   
Comment-Added-By: lars
Comment-Added-When: Fri Nov  6 10:26:46 PST 1998
Comment-Added:
   
Are you using NFS?
Any third party modules?
   
   No.  NFS is disabled, and we did not compile any 3rd party modules into
   the server.  The only extra module that I enabled was the status
   module.  The server ran fine for about 6 months before this started.  Is
   there anything in the OS itself that may have changed to cause this
   problem?
 
 Did you upgrade your kernel version or any libraries, especially libc
 around when it started happening?
 
 
 


Re: mod_auth-any/3362: Password File is not parsed correctly

1998-11-08 Thread Dirk-Willem van Gulik
The following reply was made to PR mod_auth-any/3362; it has been noted by 
GNATS.

From: Dirk-Willem van Gulik [EMAIL PROTECTED]
To: Kenny Gardner [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: mod_auth-any/3362: Password File is not parsed correctly
Date: Sun, 8 Nov 1998 11:50:52 +0100 (MET)

 On 8 Nov 1998, Kenny Gardner wrote:
 
  Number: 3362
  Category:   mod_auth-any
  Synopsis:   Password File is not parsed correctly
  Confidential:   no
  Severity:   serious
  Priority:   medium
  Responsible:apache
  State:  open
  Class:  sw-bug
  Submitter-Id:   apache
  Arrival-Date:   Sat Nov  7 17:10:00 PST 1998
  Last-Modified:
  Originator: [EMAIL PROTECTED]
  Organization:
  apache
  Release:1.2.6 and prior (and above?)
  Environment:
  BSD/OS gapdev.com 3.1 BSDI BSD/OS 3.1 Virtual Kernel #12: Fri Jun 19 
  14:32:14 MDT 1998
  
  gcc version 2.7.2.1
  
  Description:
  Password Files that are not in the format of:
  
userid:password
  
  are not parsed correctly.
 
 As you can see in the manual page; .../docs/mod/mod_auth.html password
 files for 1.2.6 are to be in the above format.
 
 Some later versions of apache accomodate the 'passwd(8)' format.
 
 Dw.
 
  This:
  
userid:password:7100:100:Staranet Admin:/:ftp;mail
  
  returns a password of:
  
password:7100:100:Staranet Admin:/:ftp;mail
  
  Anything after the first : is considered to be the Password.
  How-To-Repeat:
  Use your /etc/passwd file for authentication or any password file that 
  contains extra information after the password field.
  
  
  Fix:
  authenticate_basic_user() function in mod_auth.c:
  
 Just before:
  
 /* anyone know where the prototype for crypt is? */
  
 if (strcmp(real_pw,(char *)crypt(sent_pw,real_pw)))
  
  
 Add:
  
 {
 char *real_pwptr = real_pw;
  
 while (*real_pwptr)
{
if (*real_pwptr == ':')
   {
   *real_pwptr = 0;
   break;
   }
  
++real_pwptr;
}
 } 
  Audit-Trail:
  Unformatted:
  [In order for any reply to be added to the PR database, ]
  [you need to include [EMAIL PROTECTED] in the Cc line ]
  [and leave the subject line UNCHANGED.  This is not done]
  [automatically because of the potential for mail loops. ]
  [If you do not include this Cc, your reply may be ig-   ]
  [nored unless you are responding to an explicit request ]
  [from a developer.  ]
  [Reply only with text; DO NOT SEND ATTACHMENTS! ]
  
  
  
  
 


config/3363: Problems with Virtual hosts

1998-11-08 Thread Tim Dunton

Number: 3363
Category:   config
Synopsis:   Problems with Virtual hosts
Confidential:   no
Severity:   critical
Priority:   medium
Responsible:apache
State:  open
Class:  support
Submitter-Id:   apache
Arrival-Date:   Sun Nov  8 04:30:00 PST 1998
Last-Modified:
Originator: [EMAIL PROTECTED]
Organization:
apache
Release:1.3.3
Environment:
Solaris 2.6 with 1.3.3 Apache. I used gcc 2.7.7, I think.
Description:
I keep getting this come up when I start httpd.

[Sun Nov  8 12:23:07 1998] [error] VirtualHost www.connectfree.2b.co.uk:80 -- mi
xing * ports and non-* ports with a NameVirtualHost address is not supported, pr
oceeding with undefined results
[Sun Nov  8 12:23:07 1998] [error] VirtualHost jobs.globalgoldnetwork.co.uk:80 -
- mixing * ports and non-* ports with a NameVirtualHost address is not supported
, proceeding with undefined results
[Sun Nov  8 12:23:07 1998] [error] VirtualHost www.globalgoldnetwork.co.uk:80 --
 mixing * ports and non-* ports with a NameVirtualHost address is not supported,
 proceeding with undefined results
[Sun Nov  8 12:23:07 1998] [error] VirtualHost www.2bmail.co.uk:80 -- mixing * p
orts and non-* ports with a NameVirtualHost address is not supported, proceeding
 with undefined results
/web/apache/sbin/apachectl start: httpd started
How-To-Repeat:
My config file can be found at http://www.2b.co.uk/httpd.conf
Fix:
It is something up with virtual host, but I don't know what.
Audit-Trail:
Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]





Re: os-linux/3345: Apache compiled but did not start (shared modules)

1998-11-08 Thread Lars Eilebrecht
The following reply was made to PR os-linux/3345; it has been noted by GNATS.

From: Lars Eilebrecht [EMAIL PROTECTED]
To: (Apache GNATS) [EMAIL PROTECTED]
Cc:  Subject: Re: os-linux/3345: Apache compiled but did not start (shared 
modules)
Date: Sun, 08 Nov 1998 05:39:40 +0100 (CET)

 --Forwarded message--
 
 From: Sven Anders [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Re: os-linux/3345: Apache compiled but did not start (shared modules)
 
 [...]
 
 The gcc was ok.
 It was the glibc. glibc-2.0.6 did NOT work !
 I updated to 2.0.7 and now all runs smoothly! :-)
 
 Thanks for all!
 
 Greetings
  Sven
 
 -- 
  I am the embodiment of modern medicine.  Der Dativ ist dem 
  The holographic doctor, USS-Voyager  Genitiv sein Tod. 
 
  
  http://www.fmi.uni-passau.de/~anderss  email: [EMAIL PROTECTED] 
 
 --End of forwarded message-
 


Re: config/3363: Problems with Virtual hosts

1998-11-08 Thread marc
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]


Synopsis: Problems with Virtual hosts

State-Changed-From-To: open-feedback
State-Changed-By: marc
State-Changed-When: Sun Nov  8 10:44:42 PST 1998
State-Changed-Why:
What does running httpd -S say?



Re: config/3363: Problems with Virtual hosts

1998-11-08 Thread marc
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]


Synopsis: Problems with Virtual hosts

State-Changed-From-To: feedback-closed
State-Changed-By: marc
State-Changed-When: Sun Nov  8 11:07:03 PST 1998
State-Changed-Why:
User reports problem solved.



general/3364: I really do not know.

1998-11-08 Thread Mike Miller

Number: 3364
Category:   general
Synopsis:   I really do not know.
Confidential:   no
Severity:   non-critical
Priority:   medium
Responsible:apache
State:  open
Class:  support
Submitter-Id:   apache
Arrival-Date:   Sun Nov  8 13:20:01 PST 1998
Last-Modified:
Originator: [EMAIL PROTECTED]
Organization:
apache
Release:1.3.2
Environment:
Ok, I am not sure if this is a bug or anything, but for some reason it is not 
working in win95.
I get this error and would like to know what to do to get it to work.
 HTTPd: cannot determine localhost name.
 Use the ServerName directive to set it manually.
How would I fix it? Please be specific.
Description:
Ok, I am not sure if this is a bug or anything, but for some reason it is not 
working in win95.
I get this error and would like to know what to do to get it to work.
 HTTPd: cannot determine localhost name.
 Use the ServerName directive to set it manually.
How would I fix it? Please be specific.
How-To-Repeat:
I just ran the apace.exe file.
Fix:
No, I am new at this stuff, and that is why I emailed here.
Audit-Trail:
Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]





Re: general/3364: I really do not know.

1998-11-08 Thread marc
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]


Synopsis: I really do not know.

State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Sun Nov  8 13:23:16 PST 1998
State-Changed-Why:
This is NOT an appropriate place to be asking such basic
configuration questions.  You are pointed to places such
as Usenet for such things before you submit a PR.

The ServerName directive is a directive that you have to
set.  Oddly enough, you should set configuration params for
Apache in the Apache config files which are in the conf
directory.
Synopsis-Changed-From: I really do not know.
Synopsis-Changed-To: user can't read
Synopsis-Changed-By: marc
Synopsis-Changed-When: Sun Nov  8 13:23:16 PST 1998



Re: suexec/3357: unable to specify doc_root to be other than $(datadir)/htdocs for suEXEC

1998-11-08 Thread lars
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]


Synopsis: unable to specify doc_root to be other than $(datadir)/htdocs for 
suEXEC

State-Changed-From-To: open-closed
State-Changed-By: lars
State-Changed-When: Sun Nov  8 13:26:12 PST 1998
State-Changed-Why:

Two new options (--suexec-docroot and --suexec-logfile)
have been added to APACI to allow full control of
the suEXEC setup.




Re: suexec/3361: Suexec always report the following error command not in docroot

1998-11-08 Thread lars
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]


Synopsis: Suexec always report the following error command not in docroot

State-Changed-From-To: analyzed-closed
State-Changed-By: lars
State-Changed-When: Sun Nov  8 13:27:05 PST 1998
State-Changed-Why:

Two new options (--suexec-docroot and --suexec-logfile)
have been added to APACI to allow full control of  
the suEXEC setup.   




Re: suexec/3316: DOC_ROOT and LOG_EXEC are set in Makefile and override suexec.h

1998-11-08 Thread lars
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]


Synopsis: DOC_ROOT and LOG_EXEC are set in Makefile and override suexec.h

State-Changed-From-To: open-closed
State-Changed-By: lars
State-Changed-When: Sun Nov  8 13:28:17 PST 1998
State-Changed-Why:

Two new options (--suexec-docroot and --suexec-logfile)
have been added to APACI to allow full control of  
the suEXEC setup.   

Release-Changed-From-To: 1.3.2 and 1.3.3-1.3.3
Release-Changed-By: lars
Release-Changed-When: Sun Nov  8 13:28:17 PST 1998



Re: general/3364: I really do not know.

1998-11-08 Thread Marc Slemko
The following reply was made to PR general/3364; it has been noted by GNATS.

From: Marc Slemko [EMAIL PROTECTED]
To: Mike Miller [EMAIL PROTECTED]
Cc: Apache bugs database [EMAIL PROTECTED]
Subject: Re: general/3364: I really do not know.
Date: Sun, 8 Nov 1998 13:54:07 -0800 (PST)

 On Sun, 8 Nov 1998, Mike Miller wrote:
 
   State-Changed-From-To: open-closed
   State-Changed-By: marc
   State-Changed-When: Sun Nov  8 13:23:16 PST 1998
   State-Changed-Why:
   This is NOT an appropriate place to be asking such basic
   configuration questions.  You are pointed to places such
   as Usenet for such things before you submit a PR.
   
   The ServerName directive is a directive that you have to
   set.  Oddly enough, you should set configuration params for
   Apache in the Apache config files which are in the conf
   directory.
   Synopsis-Changed-From: I really do not know.
   Synopsis-Changed-To: user can't read
   Synopsis-Changed-By: marc
   Synopsis-Changed-When: Sun Nov  8 13:23:16 PST 1998
   
   
  Ok, First of all, I would like to tell you that you are really good at
  returning messages fast.
  Next, I would like to know where exactly is the file that I am
  supposed to edit?
 
 The bug database is for bug reports, not for basic configuration
 assistance. We do not have the resources to individually tell everyone how
 to perform basic configuration of their server.
 
 As the bug reporting page says:
 
  If you're not sure that your problem is specifically related to a  
  bug in Apache (i.e., not something like a client problem or
  configuration problem), we strongly recommend that you check in the
  comp.infosystems.www.servers.unix or 
  comp.infosystems.www.servers.ms-windows (depending on the platform
  being used) Usenet newsgroup first. If you don't receive a response
  within a few days, then please submit it to the Apache bug   
  database. If it's a known issue, you'll probably get a faster
  response from the newsgroup and you will help keep developer time  
  free for improving Apache. Most bug reports submitted are actually 
  user configuration problems that could be easily fixed by asking in
  the newsgroup.
 
  If you do not have access to a Usenet server, there are several web
  sites on the Internet that allow you to read and post to Usenet,  
  such as Deja News.  
 
 Please follow that advice.  It is there for a reason.  
 


mod_proxy/3365: Proxy: error writing to cache file

1998-11-08 Thread Krzysztof Czuma

Number: 3365
Category:   mod_proxy
Synopsis:   Proxy: error writing to cache file
Confidential:   no
Severity:   non-critical
Priority:   medium
Responsible:apache
State:  open
Class:  sw-bug
Submitter-Id:   apache
Arrival-Date:   Sun Nov  8 15:50:00 PST 1998
Last-Modified:
Originator: [EMAIL PROTECTED]
Organization:
apache
Release:1.3.3
Environment:
SunOS jantar 5.4 Generic_101946-52 i86pc i386
Description:
From time to time Proxy Server can't complete GET . because it can't
write to cache file.

Error_Log:
[Sun Nov 8 08:17:02 1998] [error} [client 195.117.6.1] (131) Connection
reset by peer: proxy: error writing to cache file /opt/proxy/tmpa0052V
How-To-Repeat:

Fix:

Audit-Trail:
Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.  ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]