Network Slave Auto Start

[Frutiger]

With Indigo 2, the network slave feature was bootable as a separate application on OSX. I was a big fan of this capability as it allowed me to set my render slave computer up to autoboot that application on startup and be ready to go at all times.

Unless I'm missing something, It seems that this feature has been removed in Indigo 3.

Is there a workaround that would allow me to get this working again?

[Zom-B]

Should be possible via Command Line / Apple Script
On windows it looks like that:

Code: Select all

cd PATH/Indigo_folder
START /B /BELOWNORMAL indigo.exe -n s -frame_upload_period 30

[Frutiger]

Good idea. I'll see if I can't learn how to do that.

[AdminHam]

Sorry to pick up on an old thread, but I have the same issue with the latest Mac version of Indigo Renderer.
We run Indigo Renderer in several computer labs. I used to be able to configure computers to run as network slaves while no one was logged in (excellent!).
I haven't been able to achieve this with the latest version. Even Network Slave during screensaver, like the Windows version has would be great.

Anyone been able to achieve this, and/or is it on the cards for official development?

[OnoSendai]

Using the switch

-n s

will start the Indigo GUI in network slave mode, is this sufficient?

[Frutiger]

Using the switch

-n s

will start the Indigo GUI in network slave mode, is this sufficient?

I think I almost know what that means.

Sooo, I put that little data into some magical place and then when it boots it will automatically book straight into network slave mode.

I'm not quite sure though; where do I put that little bit of text to make it work?

[OnoSendai]

Some kind of shell script or wrapper will be needed. I'll have another look at this at work tomorrow

[Frutiger]

Some kind of shell script or wrapper will be needed. I'll have another look at this at work tomorrow

Thanks OnoSendai!

[AdminHam]

Using the switch

-n s

will start the Indigo GUI in network slave mode, is this sufficient?

Yes, and this worked previously as a LaunchDaemon:
[/Applications/Indigo/Indigo.app/Contents/MacOS/IndigoConsole -n s]
However the latest version of Indigo seems to not like the root user running the process...?