Starting or Stopping Web Security ServicesOccasionally, you may need to stop or start a Websense service. For example, Filtering Service must be stopped and started after customizing default block messages.
When Filtering Service is started, CPU usage can be 90% or more for several minutes while the Websense Master Database is loaded into local memory.
1. Open the Windows Services console (Start > All Programs > Administrative Tools > Services).
2. Right-click a service name, and then select Start, Stop, or Restart. Restart stops the service, then restarts it again immediately from a single command.Refer to Stopping and starting principal components for the correct order to use when stopping or starting multiple Websense services.
Restarting stops a daemon, then restarts it immediately from a single command. If Websense components are spread across multiple machines, be sure that Policy Broker and the Policy Database are stopped last and started first. See Stopping and starting principal components for the preferred stopping and starting order.
2.
2. Enter the following command: ./WebsenseDaemonControl.A list of installed components is displayed, showing whether each process is running or stopped.
4. When stopping individual components on Windows machines, or when stopping components spread across multiple machines, stop the optional components first, and then the principal components, ending with the following, in the order shown:When starting services, reverse this order. It is especially important that you begin with the following services, in the order shown:Also remember that if you are stopping and starting services on the TRITON Unified Security Center machine, you may need to stop or start the following as well: