The following reply was made to PR os-irix/1727; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Lars Slettjord <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: os-irix/1727: I get 'accept_mutex_on: Permission denied' in the error_log Date: Fri, 23 Jan 1998 17:19:58 -0700 (MST) On 23 Jan 1998, Lars Slettjord wrote: > I suspected this had something to do with the various ways to do > accept serialization code, so I recompiled with -DUSE_FCNTL_SERIALIZED_ACCEPT > (which is used with the 1.2.5 version), and the new version has worked fine > (so far). But isn't this a suboptimal solution? My server don't have > multiple > processors, so USE_USLOCK_SERIALIZED_ACCEPT is probably not a good idea. But > will USE_SYSVSEM_SERIALIZED_ACCEPT be faster than > USE_FCNTL_SERIALIZED_ACCEPT? It is faster, but I normally wouldn't worry about it unless you get a lot of traffic. > > I suspect that my problem with USE_SYSVSEM_SERIALIZED_ACCEPT is due to > the absence of some important system files in my chrootet environment, but > so far I have not found any helpful hints in any of the logs, or in any > of the man-pages I've been through (semop, semctl, semget, intro). > > Could you possibly give me some hints on where to look? If you need to know > more about my chroot-setup I'll be happy to provide all the details. Try copying the whole /dev directory to the chrooted environment then if it works removing things until it breaks.
