httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "manaay <mlampret@email.si>" <mlamp...@email.si>
Subject Re: [emerg] (28)No space left on device: Couldn't create accept lock
Date Fri, 17 Jan 2003 15:24:53 GMT
I am also getting this error. Do you know how to solve the problem?

thanks,
Miha

--- In new-httpd@yahoogroups.com, Jeff Trawick <trawick@a...> wrote:
> Stas Bekman <stas@s...> writes:
> 
> > After starting the server for many times I've received:
> > 
> > [Tue Jan 14 15:55:36 2003] [emerg] (28)No space left on device:
> > Couldn't create accept lock
> > 
> > I figured out that it was the ipc device that run out of space on the
> > allocated segment, because I had encountered this problem before.
> > 
> > Is it possible to make that error message more descriptive, so users
> > won't have to wonder what device the error message is talking about?
> 
> (shields up :) )
> 
> The best compromise may be for APR to have an error code that is used
> just for when SysV IPC returns ENOSPC.  Techies will want to know that
> the kernel returned ENOSPC, but just representing it as ENOSPC like we
> do today results in an error description that doesn't help users.
> 
> -- 
> Jeff Trawick | trawick@a...
> Born in Roswell... married an alien...


Mime
View raw message