Hay itriix, I believe network restarts or reboots are necessary for those changes. Also from googling it looks like all this stuff is a bit different on OS X compared to linux. From a google link:
If you have trouble with your DHCP server changing your hostname on you, it can be VERY frustrating to figure out. For increased Googability, I’m posting this here.
The Leopard way to insure that your hostname doesn’t change on you is: sudo hostname my-permanent-name; sudo scutil –set LocalHostName $(hostname); sudo scutil –set HostName $(hostname)
That should make “my-permanent-name” survive reboots and connections to corporate and hotel networks. However, you may still find the DHCP assigned name used in System Preferences>Sharing if your network has an exceptionally oppressive setup (like my company has).
Maybe it's possible there is some inconsistency here and there? Or really, it could be the problem has nothing to do with this. :?
hey DaJuice ~ not quite sure, but i looked at my friends computers config files, that were going FAST, and they did not have any of this kind of information in their config files… in fact, their config files looked pretty much identical.
to you and everyone else:
this weekend i tried a few more things… no luck still. i tried houdini on my friends macbookpro (should be WAY slower than my 8 core mac pro)… and in fact, rendering a sphere takes about 1-2 seconds on their computer, whereas mine is still taking 17 seconds a frame… and over 30 frames taking about 7 minutes….
they were using houdini 9.5 however, so i decided to install 9.5 on my computer again and see if this did anything differently. nope. still super slow.
to reiterate some of what i've already said in earlier posts:: i reformatted my computer, installed a the new MAC OS X LEOPARD 10.5.7 and then installed HOUDINI 10 right after this, without touching ANY preferences or settings or anything. COMPLETELY DEFAULT SETTINGS!
As soon as houdini starts up, i get the rebuilding ui cache message… this is annoying but not the worst part about all of this. however i think this points to some kind of “issue” though. Because there is no reason why a DEFAULT install of leopard, with a fresh install of houdini, is causing these kinds of problems.
so I created a ROOT user account, logged in, and ran houdini. This problem goes away! The rebuilding cache message goes away! Strange. Like i said, this is a default never been touched OS! NOTHING has changed. So why is there ANY of this “permission” based problems occuring? I DEFINATELY should not have to be logged in as ROOT to use houdini to get rid of this message! And because this is a default OS install, I shouldn't even have to do any kind of workarounds. It should just work.
Okay and then once again the REAL problem at hand. HOUDINI is being super slow when rendering. 7 minutes for a sphere. VERY VERY crazy. Especially on a computer with my specs too. I also like i said before, have compared this with other programs, and ALL of the rendering and such works as it always has. Therefore pointing to the idea that the HARDWARE stuff in my comp is good. that this MUST be something to do with Houdini, Mac OS X, and 8 core early 2008 Mac Pro, and possibly, the “COMPUTER NAME” which seems very ridiculous I know, but somehow these are the ONLY things that can be a factor. Because other stuff I've stated before, IF I TURN OFF ALL NETWORK SETTINGS, this problem occurs then too.
Lastly, I've even reformatted, very time consuming on this side since I need to reinstall all of my software, and i'm actually super busy right now, so this is kind of tough for me. but, i have one more idea, which i'll try right now, and if this doesn't work, i truly will have to move passed the “reformatting” stage, as a testing ground and begin resetting up my comp again. Hopefully having given enough information to help get some fix for this issue. Last thing i'll do is: REFORMAT one more time, but this time, without giving my computer a name. For those of you that have kept up with this topic, originally i noticed the problem occur, when I “NAMED” my computer, because it had always been default, and then i named it, and the problem occured, and i tried tons of workarounds and fixes with none working, so then, i reformatted, and named my computer BEFORE installing houdini. Now this time, i'll reformat and not give my computer a name and reinstall. THIS SHOULD TECHNICALLY put things back to the original way they used to be before this occured. let's see. i'll post back soon
thanks for those who are reading and trying to help out, i'm a little frustrated because i've run out of ideas… and my entire thesis uses houdini, which “timing-wise” i am in the process of presenting very very soon. i'm getting to the “RENDERING” stage, and this is going to really hurt if it's working this slow for this part of the work Jonathan