Harlequin RIP SDK
Data Fields
RF_REPLY_FARM_STOP_PROGRESS Struct Reference
RIP Farm: API and Library to split jobs across multiple RIPs » Interface for receiving messages from the RIP farm » Extract messages to a C structure » Notification message structures

The structure of a Farm Stop Progress reply message. This notification is sent on a regular basis after a farm stop has been requested should the farm not stop in a timely fashion. The most likely reason for a farm stop not happening in a timely fashion is because: More...

#include "rf_reply_msgs.h"

Data Fields

int n_reasons
 
RF_FARM_STOP_REASON ** reasons
 

Detailed Description

The structure of a Farm Stop Progress reply message. This notification is sent on a regular basis after a farm stop has been requested should the farm not stop in a timely fashion. The most likely reason for a farm stop not happening in a timely fashion is because:

  • The raster manager has unhandled pages which need handling before the farm will stop (RF_STOP_REASON_RASTER_JOBS and RF_STOP_REASON_RASTER_PAGES_UNHANDLED).
  • A satellite blade controller has not announced that it has stopped for some reason (crash, network failure etc.). Note, there will always be at least 1 blade if this notification is received (the central blade controller). If the raster manager has unhandled pages, you should not expect the central blade controller to have exited yet.

Field Documentation

◆ n_reasons

int RF_REPLY_FARM_STOP_PROGRESS::n_reasons

How many reasons do we have for why the farm has not yet stopped.

◆ reasons

RF_FARM_STOP_REASON** RF_REPLY_FARM_STOP_PROGRESS::reasons

Array of the reasons why the farm has not yet stopped.

The documentation for this struct was generated from the following file: