[peruser] Possible bug with permission/kill

Jille jille at quis.cx
Thu May 8 10:54:58 MDT 2008


Hello,

First of all: I really like the idea of peruser.
I came up with (a proposal for) something similar last week,
and Lazy redirected me to this.

While reading through the code I saw this:

[...]
int reap_children(int *exitcode, apr_exit_why_e *status)
{
     int n, pid;

     for (n = 0; n < ap_max_daemons_limit; ++n) {
         if (ap_scoreboard_image->servers[n][0].status != SERVER_DEAD &&
                 kill((pid = ap_scoreboard_image->parent[n].pid), 0) ==
-1) {
[...]

Isn't it possible that the kill(pid, 0) fails with EPERM ?
I haven't found out yet whether reap_children is ran as root, or this is
only about other processes with the same uid.

It might be a bug, I don't know; I'm reporting it, just in case ;)
(or else I will at least learn something about peruser :))

-- Jille



More information about the Peruser mailing list