# Copyright (c) 1998 University of Southern California. # All rights reserved. # # Redistribution and use in source and binary forms are permitted # provided that the above copyright notice and this paragraph are # duplicated in all such forms and that any documentation, advertising # materials, and other materials related to such distribution and use # acknowledge that the software was developed by the University of # Southern California, Information Sciences Institute. The name of the # University may not be used to endorse or promote products derived from # this software without specific prior written permission. # # THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. LSAM LOGDAEMON PROCESS ====================== LSAM Authors: Lars Eggert $Revision: 1.2 $ ($Date: 1998/07/02 23:42:41 $) Document Version 1.1 (6/15/98) Introduction ------------ The LSAM Apache distribution runs a logdaemon process that analyzes both the proxy and server URL request histories. That history data is used to extract two sets of the most popular URL groups: that seen by the proxy and that seen by the server. These sets are suggestions by the logdaemon for the joining to a multicast channel by the proxy, or the creation of a multicast channel by the server. Those two sets are exposed to the LSAM Apache administrator via the forms-control web pages. To access those web pages see: http://server:port/cgi-bin/lsam/configure.pl Where "server:port" should be replaced with the server name and port number where your proxy server resides. Access this URL and you will be prompted for a username and password. Authorized users should enter: lsam-root:root. Guests should enter: guest:. From those control pages, the administrator can also clear the logdaemon process' internal history states and cause it to recreate those states by reading the entire existing access log or reading that log from a specified date/time until currently. The logdaemon periodically updates its request histories by reading newly added access log entries. This periodic procedure may result in changes being made to the sets of popular URL groups. Those changes will be reflected in the forms-control web pages. Both the period length and the sizes of the sets of most popular proxy and server URL groups may be reset from the forms-control web pages.