Hello, You can download the latest stable openhpi source code from http://prdownloads.sourceforge.net/openhpi/openhpi-2.12.0.tar.gz?download
You can modify, compile and install in your system. By default, the openhpi ERROR messages are logged in the syslog. You can find the openhpi error messages at /var/log/messages file in RedHat/Suse. In Ubuntu/Debian the error messages are put in /var/log/syslog file. If you are interested in DEBUG messages, set the OPENHPI_DEBUG environment variable to YES. (export OPENHPI_DEBUG=YES). Run the openhpid in foreground mode (openhpid -c <openhpi conf> -n). All the debug messages will be printed on to the terminal/console. By enabling the OPENHPI_ERROR environment variable, you can see the error messages on the terminal/console. You can also use the gdb to understanding the flow and for debugging. Please remember that you need to run the openhpid in foreground (-n) option when using gdb. Regards, Raghavendra On Tue, 2008-07-29 at 05:31 +0000, grisha gringauz wrote: > Thank you very much for your help. > As I understood, the log is written > to /tmp/log.txt.3041, /tmp/log.txt.3042, /tmp/log.txt.3043, etc? > Is there a log for openhpid itself rather than for libltdl? > About plugin.c: I run the openhpid from /etc/init.d/openhpid, after I > downloaded rpm of the openhpid. Is there a way to compile the > openhpid, so I can debug it like you say? > I saw that there is openhpid in openHPI src, but I noticed that it's a > little different from the rpm (at least the messages that it prints > are different). > > > On Wed, Jul 23, 2008 at 1:46 PM, Anton Pak <[EMAIL PROTECTED]> > wrote: > Hello! > > You can trace loading and symbol resolving by > setting LD_DEBUG, LD_VERBOSE and LD_DEBUG_OUTPUT environment > variables. ( See man ld.so ) > > i.e: "LD_DEBUG=all LD_DEBUG_OUTPUT=/tmp/log.txt openhpid" > > OpenHPI core tries to resolve plugin function, if there is no > particular > function, > it just uses NULL for it for further work. > > One can see the code and function names in src/plugin.c, > oh_load_plugin_functions function. > one can try to insert some debug printing into this code for > investigation. > > Anton Pak > > > On Wed, 23 Jul 2008 14:35:48 +0400, grisha gringauz > <[EMAIL PROTECTED]> > wrote: > > > > I wrote a plugin for openhpi and I'm trying to use the > openhpi with > > daemon. > > I suspect that the plugin doesn't work because the daemon > doesn't find > > some > > openhpi functions that I use in the plugin and that's why > lt_dlopenext of > > the plugin fails in the daemon. The plugin does work when I > use openhpi > > without daemon. > > Are there functions that exist in openhpi but not in the > daemon? > > Is there a log for the daemon? > > Thanks > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge > Build the coolest Linux based applications with Moblin SDK & > win great prizes > Grand prize is a trip for two to an Open Source event anywhere > in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Openhpi-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openhpi-devel > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
