On Wed, 16 Nov 2005, David Lee wrote:
[...]
I'm looking at another possible cause: I've been building on one machine
(relatively fast) and running it on another (old and slow). Both are
S8, but there might be some subtle difference. I put some temporary
logging code into "replace/setenv.c" and seen that "putenv" is returning
"-1". This "shouldn't happen" (and on my good, S9 box all is well).
But the problem looks like probably something Sun/Solaris/my-set-up
rather than heartbeat.
So I'm now (slowly!) rebuilding completely from scratch, on my (slow)
runtime machine so that things should be more consistent.
Still bad. Still getting error return from setenv (-> OS putenv).
But I think I've found the problem area. The heartbeat code does things
directly with the (system provided) "environ" variable. One such example
is in "lib/clplumbing/setproctitle.c:set_proc_title()".
A local test commenting most of the heart of "set_proc_title()" restores
sanity: putenv() works cleanly and successfully. And that means that
heartbeat 2.0.x can actually now run on Solaris-8!
Clearly, the code's dabbling directly with environ can upset "putenv()"
on some OSes. I'll try to tidy this up.
--
: David Lee I.T. Service :
: Senior Systems Programmer Computer Centre :
: Durham University :
: http://www.dur.ac.uk/t.d.lee/ South Road :
: Durham DH1 3LE :
: Phone: +44 191 334 2752 U.K. :
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
