Client Info

Description/Info

This description can be shown in rrControl, client table.

Location - Floor / Room

This description can be shown in rrControl, client table.

This is a Cloud Connector

If the rrClient was created/started via the rrCloudManager, then this flag is enabled.

Cost per hour override

You can override the rendering cost of this client if it is more or less than the global value you have set in rrConfig tab Other

Watt per hour override

The "Watt" counter can be used for anything.  
By default we named it "Watt" but the measure unit can be change in menu Server / Misc.
You can count anything.

We use to for example to enter the Watt usage of the machine while it is rendering.




Config presets


You can setup the configuration of a client in two different ways:

Config Preset

There are two ways to set the config of a client:

  • All settings are local to the rrClient
  • You use presets



Config presets can be selected in the client table

Render License Group

You can set a different number of licenses for different parts of your render farm

Render license groups are set in menu RenderApps / Render Licenses

Drive Mapping

You can set different drive mappings for different regions.

Drive mappings are setup in menu Files / Paths and Drives




Hardware CPU/GPU

At startup, the rrClient tests the Processor Speed of the rrClient, the number of GPUs and the speed of the GPUs.

This information is shown here.

You can change the number of GPUs in case the rrClient was not able to recognize your GPU.


Wake On Lan


If you setup WOL (Wake On LAN), then RR can boot machines.
Either initiated by you (manually, via rrControl) or the rrServer (for a job or before your working hours).

If WOL does not work, please see the Troubleshooting section.


Is is recommended to use WOL in conjunction with "Auto Shutdown". 
If there are no jobs the machines shut down and woken up if you send new jobs.



Auto WOL for render jobs

If there are a sufficient number of frames to render, the rrServer wakes additional Clients.

Auto WOL before working hours

This machine is woken up right before the working hours set for this client.

Disable Auto WOL

You can set a time range in which the rrServer should not send WOL commands to this client

Hardware -  Wake On Lan

MAC address

The MAC address of the machines network card. If the machine has multiple network cards, please be sure it uses the right one. 

If the MAC address is not set, then the client tries to find the right MAC address. 
At first it will check for active ones and then compares the IP with the rrServer IP.

MAC address - clear

This command clears the MAC address for all selected Clients.
This re-triggers the function to read the MAC address from your network card at the rrClient.

IP Range

The first three numbers of the IP address of the machine. 
Required for some of the ways to send a WOL command. 
Please see rrConfig menu Clients /Global for more information.

WOL is supported by this client

Enable this option if the machine supports WOL. RR uses the WOL method "Magic Packet". 

Be sure it is enabled in the BIOS of the machine and/or in the system settings of the OS.

for 


Working hours of the artist


"Working Hours" define the typical times when the artist is working on the machine.

(Is is "Working Hours" of the Artist, NOT "Working Hours" of the client).


Working hours:  from ... to

Sets the working hours of the artist.

Disable job thread during working hours

The selected job threads of the rrClient will not accept any jobs.
Jobs that are running are aborted.

Ignore "Disable Thread" if 
nobody is logged in

If nobody is logged in, the rrClient may take any job.

If an artist is logs in, then the rrClient will disable itself and abort any jobs that are rendering.

If the artists logs out, the rrClient enables itself again.

So if an artist is not at the company (e.g. vacation, sick), the client is rendering.

Ignore "Disable Thread"  if 
user ... is logged  in

If you have for example a user for maintenance or software installation.
Example case:
Your IT admin logs in with that account and starts some processes/installs.
The IT admin continues to work on other machines and does not log out.
Which means the machine is not really used and can render.

If thread is disabled, still accept jobs of ...
user logged in

If this rrClient is your workstation and you send a job, it renders on your machine.

If thread is disabled, still accept jobs of ...
[ ]

You can specify project, user render applications that can still render during working hours.


Auto Shutdown

Shutdown if idle for x min.

If the client did not got anything to render for x minutes, then it will shutdown itself.

Force Shutdown (kills apps) 

Windows: If enabled, then Windows will kill all applications that refuse to close on shutdown.

Even if a user is logged in

The client shuts down even if someone is logged in. You should not do this at an artist workstation as it will close all applications he has opened.

This option should be used with "Force Shutdown".

Do not shutdown

A time table to define when a client is allowed to shutdown itself.


Note:

The "Auto Shutdown" works best in combination with "Auto WOL for render jobs".


Execute Once a Day


Clear temp directory

Clears the temp folder of the machine.

This is NOT the temp folder of the render apps that the rrClient starts. (They are cleared every time a job starts).

On Mac/Linux, this is /tmp.

On windows, it is by default the temp folder in "Documents & Settings/...."

Some companies use a system-wide option to set the temp folder for all users to e.g. C.\temp.

Synchronize time with rrServer (windows only)

The client synchronizes its system time with the time of the rrServer.

This should not be required in domains, as Windows has already a function for time synchronization. (Please ask your domain admin)



Custom script


Note: It is possible to write your own batch/shell script to be executed once a day.

Please see help section Daily Execute.


Internals




       

Startup wait time

After the rrClient application is started, it waits x seconds before it receives jobs.

So the system has time to startup.

This setting does only influence if the client is started as service/deamon.

On windows: And it has only an effect if windows was just booted up.

Use alternative shell

  • MacOS:
    Enabled: ZSH
    Disabled: CSH

  • Linux
    Enabled: Bash
    Disabled: CSH