This is becauses SESI's installer is officially designed to work with Redhat, which despite political noises doesn't seem dedicated to playing nicely with Linux Standard base, which in turn means the Houdini license server doesn't automatically start up at boot time(this is sesinetd - the license server - I'm talking about, not hserver, the local license client). Not SESI's fault, just Stupid Linux Tricks.

Anyway, I won't get into setting it up permanently - but it's trivial to start manually - go to /etc/init.d and you'll probably see a lone script there for sesinetd. As root, run it from there:

./sesinetd start

Then you should be able to start houdini up.

Cheers,

J.C.

Awesome it works!

Thanks JC…. :wink:


ps. Houdini on linux is much better! I missed it. Between the workflow and the superior memory management its enough to make the eyes gloss.

So I talked to our admin at work and he told me in order to set it up automagically I needed to edit some csh file in the /etc/ dir.


I tried to edit the csh.login but it said I should edit the csh.login.local file which did not even exist. I created it and entered these commands.

#houdini license server start
source /etc/init.d/sesinetd start

#houdini environment variables start
source /opt/hfs8.0.383/houdini_setup_bash

Of course this did not work…. because I do not know what im doing. ops:


Does anyone know what file I can edit and what commands to enter.

Make your admin do it! Sheesh, that's what they're being paid for! :roll:

1. Make sure you're root.

2. Ensure the sesinetd mentioned above is in

/etc/init.d

If it's not, copy it there.

3. Type the following:

ln -s /etc/init.d/sesinetd /etc/init.d/rc5.d/S89sesinetd

Hopefully, next time you boot, sesinetd should start. I'm doing this somewhat blindly(by that I mean I don't run a server on 9.3), but it should work.

You're deep in sysadm territory here. All the usual warnings apply.

Cheers,

J.C.

That's strange, I installed H8 on my SuSE 9.3 machine and the license tools installed just fine including the init.d startup stuff…

Hmmmm…

I'll admit to not having tried it in some time - I know it didn't work in v7 releases that I tried. SESI's comment? I do know that RH's layout of init scripts is different than SUSE.

That would be great if it did!

Cheers,

J.C.

So that command will make a pointer in /etc/init.d/rc5.d/ for anything that tries to access S89sesinetd it will look at /etc/init.d/ and open sesinetd? If that is the case you are saying that there is some script that is already trying to run the sesinetd but its just looking for the wrong file in the wrong location. What script is doing that and can I edit it?

No Warren - as mentioned, sysadmin stuff. I don't want to get into a big description of this, but essentially that rc5.d directory means “run all scripts inside with a ‘start’ param whenever the system boots into init 5 mode”. The location of these scripts, and the scripts they're linked to, tend to vary between RH and some other distros.

I can't explain the “worked fine for me” comment, though.

Cheers,

J.C.

It worked!

So following that logic I created another link like this:

ln -s /opt/hfs8.0.383/houdini_setup_bash /etc/init.d/rc5.d/S88houdini_setup_bash

However that did not work. :? I am so close I can taste full setup upon login! lol

This is why I was hesitant to get into all of this. What you've done is wrong…it won't cause any damage, but you've made a huge assumption that's incorrect.

Anyway, what you could do is put

cd /hfs
source houdini_setup_bash
cd ~

in your $HOME/.bashrc file, and it will setup for houdini without having to manually do that.


J.C.

sweet it worked… Thanks JC you rock.

ps. There is no .bashrc in the home of the root folder. Not that I plan to work while logged in as root but I am curious where the root stores its file.