• Naming 서비스
• Time 서비스
• Token 서비스
• Server 로깅 서비스
• Client 로깅 서비스
• Logging Strategy 서비스
  
  

1. 이들은 로깅, 네이밍(naming), 원격 잠금, 시간 동기화와 같은 일반적인 분산 시스템 작업을 위한 재사용가능한 컴퍼넌트를 제공합니다.
2. 이들 서비스의 소스코드는 IPC wrappers, Reactor, Service Configurator, Service Initialization, Concurrency 컴퍼넌트와 같은 ACE 기능을 다루를 법에 대한 예제를 제공합니다.
   
   

• Server_Logging_Handler : The Server_Logging_Handler class is a parameterized type that is responsible for processing logging records sent to the Server from participating client hosts. When logging records arrive from the client host associated with a particular Logging Handler object, the handle_input() method of the Server_Logging_Handler class is called which in turn formats and displays the records on one or more output devices (such as the printer, persistent storage, and/or console devices.
• Server_Logging_Acceptor : The class Server_Logging_Acceptor allocates in its handle_input() routine a new instance of class Server_Logging_Handler on the heap, and accepts connections into this Server_Logging_Handler.
  
  

• These files would vary if the services are run on NT. For example, instead of using *.so, we would have to use *.dll.
• Values for parameters can also be passed in using environment variables. For example, instead of specifying absolute hostname or port numbers in the config file, we can use $HOST and $PORT, respectively, in the file (assuming that these environment variables have been set).
• If the environment variable LD_LIBRARY_PATH (in the case of UNIX) or PATH (in the case of Win32) contains the path to the shared object files or dll, then the config file can be further simplified. Instead of specifying a path to the shared object or dll, only the name of the shared object or dll would suffice. That is, the Service Configurator makes use of LD_LIBRARY_PATH (on UNIX) or PATH (on Win32) to look for the shared object files or dlls.
  
  

• Client_Logging_Handler : The Client_Logging_Handler class is a parameterized type that is responsible for setting up a named pipe and using it to communicate with different user processes on the same host. Once logging records arrive from these processes, the handler reads these records in priority order, performs network-byte order conversions on multiple-header fields, and then transmits these records to the Server Logging daemon across the network.
• Client_Logging_Connector : The class Client_Logging_Connector connects to the Server Logging daemon and then in its handle_input() routine it allocates a new instance of the Client_Logging_Handler on the heap.
  
  

dynamic Client_Logging_Service Service_Object * 
 ../lib/netsvcs:_make_ACE_Client_Logging_Connector() 
 "-h tango.cs.wustl.edu -p 10202"

• These files would vary if the services are run on NT. For example, instead of using *.so, we would have to use *.dll.
• Values for parameters can also be passed in using environment variables. For example, instead of specifying absolute hostname or port numbers in the config file, we can use $HOST and $PORT, respectively, in the file (assuming that these environment variables have been set). Instead of specifying a path to the shared object or dll, only the name of the shared object or dll would suffice. That is, the Service Configurator makes use of LD_LIBRARY_PATH (on UNIX) or PATH (on Win32) to look for the shared object files or dlls.
  
  

-f <flag1>|<flag2>|<flag3> (etc...)

• STDERR : Write messages to stderr.
• LOGGER : Write messages to the local client logger deamon.
• OSTREAM : Write messages to the ostream that gets created by specifying a filename (see below)
• VERBOSE : Display messages in a verbose manner
• SILENT : Do not print messages at all
  
  

-s filename

dynamic Logging_Strategy_Service Service_Object * 
 ../lib/netsvcs:_make_ACE_Logging_Strategy() 
 "-f STDERR"

"-f STDERR"

"-f STDERR|OSTREAM -s mylog"