Since this file is "opened" many times per second, it would probably be better to have a physical directory rather than traverse the symlink. I'm only guessing that there would be some extra overhead associated with the symlink traversal.
> Randy, > > That was is it. I put in a symb. link to the real tmpdir and it the > server started fine and appears to be working fine. You might want to see > if it can be listed on the known bugs page to help everyone else. > > Thanks, > > Jim Terhune > Somfaw Data Services > > > At 09:01 PM 04/30/97 -0500, you wrote: > > > >Make sure that /usr/tmp exists on your system. This path is > >hardcoded into Apache. We should probably see if there is some > >portable #define for a tmpdir on most systems. > > > > > >> >Number: 518 > >> >Category: config > >> >Synopsis: Child Processes hang > >> >Confidential: no > >> >Severity: serious > >> >Priority: medium > >> >Responsible: apache (Apache HTTP Project) > >> >State: open > >> >Class: sw-bug > >> >Submitter-Id: apache > >> >Arrival-Date: Wed Apr 30 18:20:01 1997 > >> >Originator: [EMAIL PROTECTED] > >> >Organization: > >> apache > >> >Release: 1.2b10 > >> >Environment: > >> BSDI 2.1 patch BK210-027 Complier gcc Pentium 166 w/ 64M > >> >Description: > >> Child process hang and when compiling using either FLOCK or FNCTL server > will not start and O/S reports "Cannot assign name to lock file!" > >> >How-To-Repeat: > >> > >> >Fix: > >> > >> >Audit-Trail: > >> >Unformatted: > >> > > > > > > > >
