Just an update, apparently clientupdate didn't work quite like I'd hoped and now I am completely unable to run the linux client. There are floating point errors everywhere.

I decided to try and build the client directly on one of the machines, and doing a make install even gets me a floating point error.

From make install :

if test ! -f /home/hobbit/client/etc/localclient.cfg ; then cp localclient.cfg /home/hobbit/client/etc/ ; fi

cp -fp runclient.sh /home/hobbit/client

cp -fp hobbitlaunch logfetch clientupdate orcahobbit msgcache hobbitclient*.sh bb bbcmd bbhostgrep bbhostshow bbdigest /home/hobbit/client/bin/

../build/merge-sects clientlaunch.cfg /home/hobbit/client/etc/clientlaunch.cfg

make[1]: *** [install] Floating point exception

make[1]: Leaving directory `/home/hobbit/hobbit-4.2.0/client'

make: *** [install-client] Error 2

This is the 4.2.0 with the patches from Oct 3rd applied (I thought there was a Nov 7th build yesterday, but I don't' see it on the site now)

Bill Hart

Burke Corporation

(515) 382-3575 x8406

From: Bill Hart [mailto:bill.hart at burkecorp.com] Sent: Wednesday, November 08, 2006 10:41 AM To: hobbit at hswn.dk Subject: [hobbit] getcwd cannot access parent directories

Hello all, I recently had the opportunity to re-install my hobbit server on FC6. As usual, this led me to exploring more features of Hobbit, and updating the clients to the full 4.2 release as well.

After I got the server up, and possibly after the client was updated, this error started showing up in the log file on an RHEL AS3 server:

shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory

There is no time stamp on it, so I can't tell if it's before or after the clientupdate happened or not, but it does happen every 5 minutes, which is when the client would be reporting in.

We have 2 other servers that are also RHEL AS3 on the same hardware with similar installs, and they are not exhibiting this behavior.

I checked the archives and there was a thread about a year ago about this happening on Debian, but I didn't see any real resolution, just that the client worked but kicked up the error (which is what we're seeing).

Does anyone have any suggestions or tips ?

Thanks,

Bill Hart

Computer Support Supervisor

Burke Corporation