On 1/8/99 2:55 PM Susan Mathews ([EMAIL PROTECTED]) wrote:

>Jason, 
>I think you just answered the question I posted recently, but I want to
>check. Is it only the 
>.lng and domains.tab files that are needed with the executable? Thanks to
>you who are helping out by answering questions while Stephen Turner is 
>moving.

Almost right. When you run Analog, it needs access to any configuration 
files (typicaly ananlog.cfg and optionaly manconf.cfg), the domains.tab 
file and one or two files from the lang directory depending on which 
language you have selected. It must also have write permission to the 
place the report is supposed to be sent.

The settings in analhead.h are defaults, anything except the manditory 
config file name, can be overridden in the configuration file. I generaly 
specify everything in the configuration file and ignore the defaults in 
analhead.h. Of course thats lots and lots of configuration commands.

I have attached a sample configuration file.

Jason

>               Susan 
>
>My question was:
>>I'd like my system administrator to install analog in a shared place for
>>several of us who use it for different web sites. We don't usually put the
>>full source in the executable directory, so I've been trying to figure out
>>the minimum of files which need to be there for execution. As far as I can
>>see Analog needs lang/*.lng (or at least the .lng file use here),and
>>domains.tab or it just bombs out. The analog.cfg file looks like a really
>>good idea, especially since one could override options in another .cfg
>>file. Are there other files besides "analog" which must be there? This is
>>DEC Unix (a really big Compaq now).
>
>At 01:33 PM 1/8/99 -0500, you wrote:
>>
>>HTTPDIR is not supported in configuration files. All you need to do is 
>>spell out the full path name in the configuration file. The use of 
>>HTTPDIR is just a C programing short hand to avoid repeating the path.
>>
>>To support multipule domains just set the filtering and report 
>>destination locations in each configuration file (one per domain) and run 
>>analog several times, once for each domain. The reports can have 
>>different names and all share the same lang etc. files.
>>
>>There is no need to recompile, everything can be set in the configuration 
>>file.
>>
>>Analog isn't the simplest program to configure but the configuration 
>>comands are all well documented. It would be much simpler if you worked 
>>from the documentation instead of the analhead.h file.


-----------------
[EMAIL PROTECTED]
-----------------
Dr. Seuss books . . . can be read and enjoyed on several levels. For
example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed
as a searing indictment of the narrow-minded binary counting system.
  -- Peter van der Linden, Expert C Programming, Deep C Secrets

analog.cfg.SIT.hqx

Reply via email to