1·This daemon broadcasts the information for the local machine and collects the broadcast data from all the other machines.
这个守护进程为本地计算机广播信息，并收集来自所有其他计算机的广播数据。
2·It normally runs as a daemon in the background when started.
启动后，它通常作为一个守护进程在后台运行。
3·In this case, the status of the application server needs to be checked to ensure they are all up and running and have registered with the location service daemon.
在此情况下，需要检查应用程序服务器的状态，以确保它们全都已启动和运行，并且已向位置服务守护进程注册。
4·The slot manager runs as a daemon to control the number of token slots provided to applications, and it interacts with applications using a Shared memory region.
槽管理器作为守护进程来运行以控制向应用程序提供的令牌槽数，并且使用一个共享内存区域与应用程序交互。
5·Otherwise, the daemon might fail to start properly next time, or another instance might start up later and cause contention.
否则，这个守护进程下次可能无法正常启动，或者可能稍后会启动另一个实例，从而导致争用。
1·In a production environment, I recommend putting the central manager and scheduling daemon on separate machines.
在生产环境中，建议将中央管理器和调度后台程序安排在不同的机器上。
2·Each server must be running a daemon to handle the batches of jobs - this leaves mobile devices out of the picture.
每个服务器都必须运行一个后台程序来处理众多任务，这样移动设备就不行了。
3·Before we go into the details of each of these services, you should keep in mind that all these services are implemented by a single RPC server, called a security daemon or secd.
在了解每个服务的详细信息之前，您应该记住，所有这些服务都是由一个RPC服务器实现的，该服务器称为安全后台程序或secd。
4·To avoid any possible data consistency issues during the upgrade, I shut down the HTTPD daemon and stopped the lpar2rrd script from running.
为了避免在升级过程中出现任何数据一致性问题，我关闭了httpd后台程序并停止运行lpar2rrd脚本。
5·With both systems configured, start the NTP daemon on the NIS master using
配置了两个系统后，使用以下命令在 NIS 主服务器上启动 NTP 后台程序