To quote from my original post,

What's happening is that the Apache process is dying about the time that the alarm is set. Dying is bad, in this context. OK, in any context.

Running this code from the command line works fine, this I'm trying to understand why setting an alarm (my guess, based on output from strace) might be causing the problem. After commenting out all of the calls to alarm, I'm still seeing problems: 

getgroups32(0x20, 0xbfffe2f0)           = 1
stat64("/opt/fonts-ecs-2004-07-23/mscorefonts", {st_mode=S_IFDIR|0755,
+ st_size=4096, ...}) = 0
getgroups32(0x20, 0xbfffe2f0)           = 1
rt_sigaction(SIGALRM, {0x4044fc80, [], SA_RESTORER, 0x402b88f8}, {SIG_
+DFL}, 8) = 0
pipe([9, 10])                           = 0
ioctl(9, SNDCTL_TMR_TIMEBASE, 0xbfffe1b0) = -1 EINVAL (Invalid argumen
+t)
_llseek(9, 0, 0xbfffe200, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
ioctl(10, SNDCTL_TMR_TIMEBASE, 0xbfffe1b0) = -1 EINVAL (Invalid argume
+nt)
_llseek(10, 0, 0xbfffe200, SEEK_CUR)    = -1 ESPIPE (Illegal seek)
fcntl64(9, F_SETFD, FD_CLOEXEC)         = 0
fcntl64(10, F_SETFD, FD_CLOEXEC)        = 0
pipe([11, 12])                          = 0
ioctl(11, SNDCTL_TMR_TIMEBASE, 0xbfffe1b0) = -1 EINVAL (Invalid argume
+nt)
_llseek(11, 0, 0xbfffe200, SEEK_CUR)    = -1 ESPIPE (Illegal seek)
ioctl(12, SNDCTL_TMR_TIMEBASE, 0xbfffe1b0) = -1 EINVAL (Invalid argume
+nt)
_llseek(12, 0, 0xbfffe200, SEEK_CUR)    = -1 ESPIPE (Illegal seek)
fcntl64(11, F_SETFD, FD_CLOEXEC)        = 0
fcntl64(12, F_SETFD, FD_CLOEXEC)        = 0

[download]

Something still appears to be setting an alarm

rt_sigaction(SIGALRM, {0x4044fc80, [], SA_RESTORER, 0x402b88f8}, {SIG_DFL}, 8) = 0

that I presume is breaking Apache, even though I believe I'm running under the prefork MPM.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

In reply to Re^4: mod_perl, prefork mpm and alarms by talexb
in thread mod_perl, prefork mpm and alarms by talexb

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.