Re: Apache core dump
coreadm is new to 2.7, I'm running 2.6. And to answer the next posters' question, ulimit is unlimited. I'll have to look into that dump core setuid thing, thanks, --Perry On Mon, Jun 24, 2002 at 07:02:51PM -0700, Aaron Bannert wrote: On Mon, Jun 24, 2002 at 06:32:56PM -0700, Perry Harrington wrote: I cannot for the life of me get Apache to dump a core file. I have the Coredirectory set to a writable directory, and I even modified the signal handler to simply call abort after chdir. I even tried setting the CORE rlimit size to RLIM_INFINITY. Does anyone have a clue why this is barfing? When I truss the process, it catches the signal and goes about cleaning up, the abort doesn't trigger a core file. This is driving me batty! I have the accept mutex using fcntl locking and I linked it without pthread support, so threading shouldn't be the cause. I event commented out the SIGABRT handlers so it would default to the system handler. Solaris 2.6 system, latest cluster bunch. As I understand it, this is default behavior on Solaris when running binaries that have called setuid(). See /etc/coreadm.com and coreadm(1M) for a way to override this. -aaron -- Perry Harrington Director ofzelur xuniL () perry at webcom dot com System ArchitectureThink Blue. /\ Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty or safety. Nor, are they likely to end up with either. -- Benjamin Franklin
Apache core dump
I cannot for the life of me get Apache to dump a core file. I have the Coredirectory set to a writable directory, and I even modified the signal handler to simply call abort after chdir. I even tried setting the CORE rlimit size to RLIM_INFINITY. Does anyone have a clue why this is barfing? When I truss the process, it catches the signal and goes about cleaning up, the abort doesn't trigger a core file. This is driving me batty! I have the accept mutex using fcntl locking and I linked it without pthread support, so threading shouldn't be the cause. I event commented out the SIGABRT handlers so it would default to the system handler. Solaris 2.6 system, latest cluster bunch. --Perry -- Perry Harrington Director ofzelur xuniL () perry at webcom dot com System ArchitectureThink Blue. /\ Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty or safety. Nor, are they likely to end up with either. -- Benjamin Franklin
BUG: http_vhost.c:fix_hostname
There is a bug in fix_hostname. The comment above function says that the hostname is lowercased, but it's not. the line which reads: *dst++ = *src++; in context of: goto bad; else break; } *dst++ = *src++; } /* strip trailing gubbins */ if (dst host dst[-1] == '.') { dst[-1] = '\0'; } else { should read: *dst++ = tolower(*src++); Thanks, --Perry -- Perry Harrington Director ofzelur xuniL () perry at webcom dot com System ArchitectureThink Blue. /\ Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty or safety. Nor, are they likely to end up with either. -- Benjamin Franklin