View Single Post
Old 10-01-2014, 03:49 PM   #20
rupor
meat popsicle
rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.rupor ought to be getting tired of karma fortunes by now.
 
rupor's Avatar
 
Posts: 237
Karma: 441248
Join Date: Jul 2007
Location: USA
Device: Kindles, Pixels, iPads
@eureka

Thank you for the info!

I have seen lipc-wait-event - it is quite useful in a script, but than something has to start this script and keep it running The same I think is true for linking with liblipc.so - my program has to be running and than it could register a handler and listen for the event (I will have to use upstart I think - unless there is a way to ask lipc to take care of my program lifetime). By editing a single line of /etc/lipc-daemon-events.conf I could easily avoid all of that, reduce memory footprint and simplify my code, so usage of lipc-daemon this time was intentional.

Last edited by rupor; 10-01-2014 at 03:52 PM.
rupor is offline   Reply With Quote