www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nathan Neulinger <nn...@umr.edu>
Subject os-hpux/2466: Placing logs directory in AFS causes children to be unkillable
Date Thu, 18 Jun 1998 16:20:11 GMT

>Number:         2466
>Category:       os-hpux
>Synopsis:       Placing logs directory in AFS causes children to be unkillable
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Jun 18 09:30:00 PDT 1998
>Last-Modified:
>Originator:     nneul@umr.edu
>Organization:
apache
>Release:        1.3
>Environment:
troot-falcon(288)> gcc -v
Reading specs from /afs/umr.edu/software/egcs/hpux10/lib/gcc-lib/hppa1.1-hp-hpux10.20/egcs-2.90.23/specs
gcc version egcs-2.90.23 980102 (egcs-1.0.1 release)
troot-falcon(289)> uname -a
HP-UX falcon B.10.20 A 9000/735 2006401184 two-user license
>Description:
I was testing some module development for the new server, and just put
the log directory in AFS instead of a local directory.

For some reason, this causes all the children to be completely unkillable. They
hang similarly to the way a process hung on NFS hangs. 

AFS supports fcntl locking, and in general works fine for everything else, but
something is causing this lockup.

The problem does not appear to occur with 1.2.

This isn't critical, because no one is going to run with their logs pointed into
AFS, but it does point out an potential problem.

BTW, You might consider adding WRAP=HARD WRAP=PHYSICAL to the textarea definitions
on this form.
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]




Mime
View raw message