Andy Lutomirski <luto@xxxxxxxxxxxxxx> writes: > Pid reuse is common, which means that it's difficult or impossible > to read information about a pid from /proc without races. Sigh. What we need are not race free pids, but a file descriptor based process management api. Possibly one that starts by handing you a proc directory. Which probably means that we need a proc file we can write to and send signals to a process, and another proc file we can select on and wait for the process to exit. Making pids bigger just looks like bandaid. Remember evovle things in the direction of an object capability system things wind up being more maintainable. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
