another situation where the set[ug]id thing bites

[Paul Davis <pbd op net>]

1) start up a setuid GTK application
2) create some RT scheduled threads
3) drop uid-based priviledges
4) call gtk_init()
5) call gtk_main()

.
.
.

N) dynamically load new code that needs a running
     GTK GUI to "construct" itself.
N+1) attempt to create some more RT scheduled threads

you lose. or rather, i lose. in general, doing anything
at time N that requires priviledge is a no-go.

capabilities are the right way to do this, anyway.

--p