(now I just need to find out why 'courierldapaliasd' is consuming ~50% of
my CPU, even though 'truss -f' only shows it sleeping...)
That means that the process is stuck in an internal infinite loop.
Definitely not good.
Is this a known problem, or just something out of whack on my box? Is
there something I can do to isolate the cause?
I have not heard of this before. To isolate the cause, compile with the -g
flag, and manually install courierldapaliasd by hand. Then you should be
able to attach a debugger to the process and get a stack traceback.
Well, I got the traceback. I don't really consider myself a programmer,
though, so are there any trained eys that can clue me in on what's going
#0 0xdfbb1523 in _libc_sigpause ()
#1 0xdfbea6c1 in sigpause ()
#2 0x804a60e in loop (fd=6) at ldapaliasd.c:699
#3 0x804a815 in start () at ldapaliasd.c:756
#4 0x804a9ed in main (argc=2, argv=0x8047b78) at ldapaliasd.c:832