Thanks, that worked for us too.
I am still puzzled as to why or how this happened. I am sure it's a problem with the NVIDIA driver installer, but why would it pick up the ~hobbit/client/tmp directory? It just seems too damn strange.
Regards Vernon
-----Original Message----- From: Martin Flemming [mailto:martin.flemming at desy.de] Sent: Friday, 30 November 2007 2:18 AM To: hobbit at hswn.dk Subject: RE: [hobbit] Hobbits are good sneaks
Hi !
I've got the same error a few month ago ...
.. i've deleted the tmp-link in home of hobbit
/usr/lib/hobbit/client/tmp is a link to /tmp
remove the link and create a real directory tmp in /usr/lib/hobbit/client/ ...
.. for me, it did worked ..
cheers, martin
On Thu, 29 Nov 2007, Everett, Vernon wrote:
How did you resolve it? What caused it?
Did you come up with a workaround?
It sounds like the NVIDIA drivers are the common denominator here, but
we need to update all our desktops, and this is a bit of a show-stopper.
Regards Vernon
-----Original Message----- From: Sloan [mailto:joe at tmsusa.com] Sent: Thursday, 29 November 2007 3:03 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Hobbits are good sneaks
Everett, Vernon wrote:
Hi all
OK, this is the strangest thing I have ever seen.
We are running Red Hat EL3 A few weeks back, we compiled hobbit into a rpm, and installed the client on this machine.
Now we are trying to update the video driver, and we get this.
sh NVIDIA-Linux-x86_64-169.04-pkg2.run -ans Verifying archive
integrity... OK Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64
169.04..................................................................
........................................................................
.
ERROR: Unable to create
'/usr/lib/hobbit/client/tmp/selfgz8167/NVIDIA-Linux-x86_64-169.04-pkg2 /u sr/lib32/libnvidia-cfg.so.169.04'
for copying (No such file or directory) WARNING: Unable to restore file
'/usr/lib/hobbit/client/tmp/selfgz8167/NVIDIA-Linux-x86_64-169.04-pkg2 /u sr/lib32/libnvidia-cfg.so.169.04'.
WARNING: Unable to perform the runtime configuration check for library
'libcuda.so.1' ('/usr/lib64/libcuda.so.169.04'); assuming successful
installation.
If we remove the hobbit RPM and rename the /usr/lib/hobbit directory
to something else, it works.
Has anybody seen anything like this before?
Yes, it was at least a year ago, and I was looking at hobbit-4.1.2 IIRC. It was the same sort of bizarre environment poisoning you describe, and I also saw it when trying to update nvidia drivers.
Joe
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material.
You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.