Yep, that's what it was. The box it was built on had a huge value for
shminfo_shmmax (apparently it was running oracle at one time or
another). So for now the simplest solution was to rebuild the mm
library on this particular target machine and then rebuild apache on
that box.
thanks for the help!!!
-Avery
Volker Borchert wrote:
>
> In message <[EMAIL PROTECTED]> you write:
>
> |> bash# /path/bin/httpsd-1.3.14 -f /path/etc/httpsd.portal.conf
> |> Ouch! ap_mm_create(1048576, "/path/logs/httpsd.mm.363") failed
> |> Error: MM: mm:core: failed to acquire shared memory segment (Invalid argument):
>OS: No such file or directory
>
> Sounds familiar.
>
> |> My config files are basically identical on all of the boxes.
>
> Check shmsys:shminfo_shmmax in /etc/system.
>
> When mm is built, it seems to memorize somehow its value. An apache
> built on a machine with a very large shmmax installed on a machine
> with a much smaller shmmax might ask for a shm segment larger than
> the kernel is configured for, thus the "Invalid argument".
>
> Volker
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
--
****************************
Avery Buffington
System Administrator
FundsXpress Financial Network
[EMAIL PROTECTED]
****************************
"UNIX was not designed to stop you from doing stupid things, because
that would also stop you from doing clever things." -- Doug Gwyn
S/MIME Cryptographic Signature
