Keith Palmieri wrote:
> 1. Is it a bad idea to run analog on a production server?
Depend on how much processing Analog has to do and how heavily loaded
the server is. Analog is quite fast and _very_ processor intensive when
not doing DNS lookups. In this case it can make your web server slow to
respond while it's running. If you have off-peak hours where traffic is
very low this could be fine.
If you have Analog doing DNS lookups for you, there is a lot of 'wait'
time while it looks up unknown addresses. This makes it use less
resources and put less strain on the server -- but it makes it take
longer to run.
If this is a Unix-like server you could also use 'nice'.
> 2. If we don't run analog on the production server and instead run it on a
> local server in house, is there a way to automatically ftp the log files
> from the production server to the server running analog?
There is nothing in Analog to do this -- Analog is focused on producing
statistics reports. But it wouldn't be hard to write a shell script or
Perl script to do this on a Unix system. Similar stuff can likely be
done with WSH on Windows servers and AppleScript in Mac servers.
--
Jeremy Wadsack
Wadsack-Allen Digital Group
+------------------------------------------------------------------------
| This is the analog-help mailing list. To unsubscribe from this
| mailing list, go to
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| List archives are available at
| http://www.mail-archive.com/[email protected]/
| http://lists.isite.net/listgate/analog-help/archives/
| http://www.tallylist.com/archives/index.cfm/mlist.7
+------------------------------------------------------------------------
