Re: Trying to solve file lock problem with /etc/sudoers

I figured out why sudo was not building, unless I explicitly state a umask in my .profile that is NOT umask 000, which it seemed like it was. sudo will fail some permission checks. If put either umask 002 or 022 in .profile sudo will build. So is there another bug with default file permissions then

portseal - tools to locate port management bugs

Hi :) here is another prototype of mine, also employing a source-transformation, that can detect port leaks: allocated receive port 154 test-obj/test: leaked receive right 154 test-obj/test[0x8048c36] test-obj/test[0x8048dcc] /lib/i386-gnu/libc.so.0.3(__libc_start_main+0xbc)[0x10aa69c] test-obj/t

axxxp - a field access profiler

Hi :) I'd like to share a neat hack with you. It is a field access profiler that can be used on any program written in C (well, in theory at least). I wrote it so that I can use it on gnumach. I used it to come up with 322fa73afed84fe37fb7bfe0583109ff33eb26d7. http://darnassus.sceen.net/gitweb