7.7. Enabling a Publishing Queue
Figure 7.1. Enabling the Publishing Queue
CS.cfgfile allows administrators to set other options for publishing, like the number of threads to use for publishing operations and the queue page size.
- Stop the CA server, so that you can edit the configuration files.
]# systemctl stop firstname.lastname@example.org
- Open the CA's
- Set the
ca.publish.queue.enableto true. If the parameter is not present, then add a line with the parameter.
- Set other related publishing queue parameters:
ca.publish.queue.maxNumberOfThreadssets the maximum number of threads that can be opened for publishing operations. The default is 3.
ca.publish.queue.priorityLevelsets the priority for publishing operations. The priority value ranges from
-2(lowest priority) to
2(highest priority). Zero (0) is normal priority and is also the default.
ca.publish.queue.pageSizesets the maximum number of requests that can be stored in the publishing queue page. The default is 40.
ca.publish.queue.saveStatussets the interval to save its status every specified number of publishing operations. This allows the publishing queue to be recovered if the CA is restarted or crashes. The default is 200, but any non-zero number will recover the queue when the CA restarts. Setting this parameter to 0 disables queue recovery.
ca.publish.queue.maxNumberOfThreads=1 ca.publish.queue.priorityLevel=0 ca.publish.queue.pageSize=100 ca.publish.queue.saveStatus=200
ca.publish.queue.enableto false and
ca.publish.queue.maxNumberOfThreadsto 0 disables both the publishing queue and using separate threads for publishing issued certificates.
- Restart the CA server.
]# systemctl restart email@example.com