[hobbit] Clientupdate problems

[Asif Iqbal]

2009/5/30 Alexander Bech <alex at bakarasse.de>:
> rdeal schrieb:
>> Does anyone have clientupdate working reliably for a large number of
>> machines?  I noticed a problem with clientupdate failing on our 4.2.0 server
>> and tracked it down that once a few clients seem to request the update the
>> server stops sending the file.  The clients however happily update the
>> clientversion.cfg and thus never attempt to get the file again.  After
>> upgrading to 4.2.3, the problem is the same.
>>
>> Anyone else see this?  I have read some of the back forum messages and it
>> sounds line several others have run up against this same problem but there
>> doesn't seem to be a solution.
>> Butch
>>
>>
>> To unsubscribe from the hobbit list, send an e-mail to
>> hobbit-unsubscribe at hswn.dk
>>
>>
>>
> Yes.
> I commented out the line 1975 in hobbitd.c.
>
> --- hobbitd.c.filecache-bug     2009-05-30 20:46:59.000000000 +0200
> +++ hobbitd.c   2009-02-27 13:45:56.000000000 +0100
> @@ -1972,7 +1972,7 @@
>                        }
>                }
>
> -               add_filecache(fullfn, result, st.st_size);
> +               /* add_filecache(fullfn, result, st.st_size); */
>        }
>
>        msg->buflen = st.st_size;
>
> it works.

Is that still the right fix to make clientupdate works all the time?

Out of 20 or so solaris 10 hosts only 3 of them received the update.

Rest ignored the update. Manually untarring the file as user hobbit
works fine. So permission is not an issue. All these servers are
same release of solaris

>
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe at hswn.dk
>
>
>



-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?