[hobbit] clients problems

[Henrik Stoerner]

On Wed, Jul 27, 2005 at 02:35:22PM -0400, Michael Nemeth wrote:
> hobbitclient-hpux.sh should be hobbitclient-hp-ux.sh

Yep, fixed.

> for hp-ux 11.0 and below  (I don't have hpux 11.11) configure scripts 
> could(should?)  have :
> USERDATA=`getent passwd $BBUSER 2>/dev/null || ypmatch  $BBUSER passwd  
> 2>/dev/null || grep "^${BBUSER}:" /etc/passwd`
> A there no getent for  hpux running yp (maybe one with nis+? )  .
> I was luck and was compiling mu hpux client on the yp server so it work  
> by grap /etc/passwd !

Heh, this shows I never had to work much with NIS. Thanks, I've added
this to the configure-scripts.

> Compile problems :
> hp-ux 10.20
> sendmsg.c: In function `sendtobbd':
> sendmsg.c:318: `socklen_t' undeclared (first use in this function)
> sendmsg.c:318: parse error before `connressize'
> sendmsg.c:320: `connressize' undeclared (first use in this function)
> 
> solaris 2.6
> sendmsg.c: In function `sendtobbd':
> sendmsg.c:245: warning: implicit declaration of function `inet_aton'
> sendmsg.c:318: `socklen_t' undeclared (first use in this function)
> sendmsg.c:318: parse error before `connressize'
> sendmsg.c:320: `connressize' undeclared (first use in this function)
> sendmsg.c:320: warning: passing arg 4 of `getsockopt' from incompatible pointer type

socklen_t is an unknown datatype on both of these systems. This appears
to be a common "problem", so I'll do some configuration stuff to 
try and figure this out automatically.

> IM not C programmer at all maybe these are easy fixes ,  like a missing 
> include?

If only it were that simple ... it's more an issue of the various Unix
vendors interpreting the POSIX specification differently. "socklen_t"
is actually defined in POSIX, but as you can see Solaris and HP-UX
doesn't know about it until some later versions.

> Last , I  wondering how easy it will be to build a  cilent and tar it 
> for use on another system  AND change if need BBHOME;
> I not look at this yet as anyone else? 

The files in the client/etc/ directory have the BBHOME settting embedded
in them - if you look at the hobbit source-files you'll see that 
hobbitclient.cfg and clientlaunch.cfg are generated by "make", by
replacing "@BBHOME@" in the ...DIST file with the location you configured 
the client for.

So you can tar up a client directory and move it to a different machine,
but if you change the location of the client you'll need to modify these 
files to reflect the new BBHOME setting.


Regards,
Henrik