Mailing List Archive

Brian,

"If the name of a configuration file given in a CONFIGFILE command
doesn't include a directory, it will be looked for wherever analog
expects to find its configuration files. (This location is a
compile-time option.) For example, in the Windows version it would be in
the same folder as the analog executable. This applies to the default
and mandatory configuration files as well. But configuration files given
with +g (***are relative to the current directory at the time you run
the program***). "

Perhaps absolute paths are therefore not supported? Assuming you are in
Linux I suggest you try using the dot dot notation for the parent
directory. For example:

analog +G -g../lib_analog_config/alt_config.cfg

assuming you have run the executable from
/usr/local/analog-6.03/lib_analog_config/

If you run it from ./analog-6.03/

on the other hand then you would only need to use
-g/lib_analog_config/alt_config.cfg

Regards
Richard

Brian Clanton wrote:
> I have an alternate config files that I want analog to use.
>
>
> analog +G -galt_config.cfg
>
> However, I have multiple config files, so to keep it organized, I have a
> specific directory for them:
>
> /usr/local/analog-6.03/lib_analog_config
>
> I've tried using the directory path in the statement that provides the
> location of the config file, but it doesn't seem to work properly:
>
> analog +G -g/usr/local/analog-6.03/lib_analog_config/alt_config.cfg
>
>
> What is the correct syntax to use to specify alternate config files in other
> directories?
>
> +------------------------------------------------------------------------
> | TO UNSUBSCRIBE from this list:
> | http://lists.meer.net/mailman/listinfo/analog-help
> |
> | Analog Documentation: http://analog.cx/docs/Readme.html
> | List archives: http://www.analog.cx/docs/mailing.html#listarchives
> | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
> +------------------------------------------------------------------------
>
>

+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------

AH!!

Found my error.

When I right crontabs I try to include absolute paths whenever possible. It
seems that I can invoke analog with an absolute path, but from the
analog6.03 directory, I need to omit the "/" after the "-g" switch. This is
the command that works when I want to change config files and want an
absolute path declared for the analog executable:

(The "glib" is not the gnu lib but -g and the directory "lib_analog_config"

/usr/local/analog-6.03/analog +G -glib_analog_config/ob_analog.cfg



> -----Original Message-----
> From: analog-help-bounces@lists.meer.net
> [mailto:analog-help-bounces@lists.meer.net] On Behalf Of
> Richard Hamilton
> Sent: Friday, August 15, 2008 3:19 PM
> To: Support for analog web log analyzer
> Subject: Re: [analog-help] Alternate config files
>
>
> Brian,
>
> "If the name of a configuration file given in a CONFIGFILE
> command doesn't include a directory, it will be looked for
> wherever analog expects to find its configuration files.
> (This location is a compile-time option.) For example, in the
> Windows version it would be in the same folder as the analog
> executable. This applies to the default and mandatory
> configuration files as well. But configuration files given
> with +g (***are relative to the current directory at the time
> you run the program***). "
>
> Perhaps absolute paths are therefore not supported? Assuming
> you are in Linux I suggest you try using the dot dot notation
> for the parent directory. For example:
>
> analog +G -g../lib_analog_config/alt_config.cfg
>
> assuming you have run the executable from
> /usr/local/analog-6.03/lib_analog_config/
>
> If you run it from ./analog-6.03/
>
> on the other hand then you would only need to use
> -g/lib_analog_config/alt_config.cfg
>
> Regards
> Richard
>
> Brian Clanton wrote:
> > I have an alternate config files that I want analog to use.
> >
> >
> > analog +G -galt_config.cfg
> >
> > However, I have multiple config files, so to keep it
> organized, I have
> > a specific directory for them:
> >
> > /usr/local/analog-6.03/lib_analog_config
> >
> > I've tried using the directory path in the statement that
> provides the
> > location of the config file, but it doesn't seem to work properly:
> >
> > analog +G -g/usr/local/analog-6.03/lib_analog_config/alt_config.cfg
> >
> >
> > What is the correct syntax to use to specify alternate
> config files in
> > other directories?
> >
> >
> +---------------------------------------------------------------------
> > +---
> > | TO UNSUBSCRIBE from this list:
> > | http://lists.meer.net/mailman/listinfo/analog-help
> > |
> > | Analog Documentation: http://analog.cx/docs/Readme.html List
> > | archives: http://www.analog.cx/docs/mailing.html#listarchives
> > | Usenet version:
> news://news.gmane.org/gmane.comp.web.analog.general
> >
> +---------------------------------------------------------------------
> > +---
> >
> >
>
> +-------------------------------------------------------------
> ----------
> +-
> | TO UNSUBSCRIBE from this list:
> | http://lists.meer.net/mailman/listinfo/analog-help
> |
> | Analog Documentation: http://analog.cx/docs/Readme.html List
> | archives: http://www.analog.cx/docs/mailing.html#listarchives
> | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
> +-------------------------------------------------------------
> ----------
> +-
>

+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------

Brian,

Just to avoid future confusion, what you have done there is actually to
specify a relative path not an absolute path. You have launched analog
from the analog-6.03 directory (thereby making it the present working
directory) and have then specified lib_analog_config as the directory
containing your config files, which is an immediate descendent of
analog-6.03.

The omission of the leading '/' is exactly what makes this a 'relative
path'.

R.


Brian Clanton wrote:
> AH!!
>
> Found my error.
>
> When I right crontabs I try to include absolute paths whenever possible. It
> seems that I can invoke analog with an absolute path, but from the
> analog6.03 directory, I need to omit the "/" after the "-g" switch. This is
> the command that works when I want to change config files and want an
> absolute path declared for the analog executable:
>
> (The "glib" is not the gnu lib but -g and the directory "lib_analog_config"
>
> /usr/local/analog-6.03/analog +G -glib_analog_config/ob_analog.cfg
>
>
>
>
>> -----Original Message-----
>> From: analog-help-bounces@lists.meer.net
>> [mailto:analog-help-bounces@lists.meer.net] On Behalf Of
>> Richard Hamilton
>> Sent: Friday, August 15, 2008 3:19 PM
>> To: Support for analog web log analyzer
>> Subject: Re: [analog-help] Alternate config files
>>
>>
>> Brian,
>>
>> "If the name of a configuration file given in a CONFIGFILE
>> command doesn't include a directory, it will be looked for
>> wherever analog expects to find its configuration files.
>> (This location is a compile-time option.) For example, in the
>> Windows version it would be in the same folder as the analog
>> executable. This applies to the default and mandatory
>> configuration files as well. But configuration files given
>> with +g (***are relative to the current directory at the time
>> you run the program***). "
>>
>> Perhaps absolute paths are therefore not supported? Assuming
>> you are in Linux I suggest you try using the dot dot notation
>> for the parent directory. For example:
>>
>> analog +G -g../lib_analog_config/alt_config.cfg
>>
>> assuming you have run the executable from
>> /usr/local/analog-6.03/lib_analog_config/
>>
>> If you run it from ./analog-6.03/
>>
>> on the other hand then you would only need to use
>> -g/lib_analog_config/alt_config.cfg
>>
>> Regards
>> Richard
>>
>> Brian Clanton wrote:
>>
>>> I have an alternate config files that I want analog to use.
>>>
>>>
>>> analog +G -galt_config.cfg
>>>
>>> However, I have multiple config files, so to keep it
>>>
>> organized, I have
>>
>>> a specific directory for them:
>>>
>>> /usr/local/analog-6.03/lib_analog_config
>>>
>>> I've tried using the directory path in the statement that
>>>
>> provides the
>>
>>> location of the config file, but it doesn't seem to work properly:
>>>
>>> analog +G -g/usr/local/analog-6.03/lib_analog_config/alt_config.cfg
>>>
>>>
>>> What is the correct syntax to use to specify alternate
>>>
>> config files in
>>
>>> other directories?
>>>
>>>
>>>
>> +---------------------------------------------------------------------
>>
>>> +---
>>> | TO UNSUBSCRIBE from this list:
>>> | http://lists.meer.net/mailman/listinfo/analog-help
>>> |
>>> | Analog Documentation: http://analog.cx/docs/Readme.html List
>>> | archives: http://www.analog.cx/docs/mailing.html#listarchives
>>> | Usenet version:
>>>
>> news://news.gmane.org/gmane.comp.web.analog.general
>>
>> +---------------------------------------------------------------------
>>
>>> +---
>>>
>>>
>>>
>> +-------------------------------------------------------------
>> ----------
>> +-
>> | TO UNSUBSCRIBE from this list:
>> | http://lists.meer.net/mailman/listinfo/analog-help
>> |
>> | Analog Documentation: http://analog.cx/docs/Readme.html List
>> | archives: http://www.analog.cx/docs/mailing.html#listarchives
>> | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
>> +-------------------------------------------------------------
>> ----------
>> +-
>>
>>
>
> +------------------------------------------------------------------------
> | TO UNSUBSCRIBE from this list:
> | http://lists.meer.net/mailman/listinfo/analog-help
> |
> | Analog Documentation: http://analog.cx/docs/Readme.html
> | List archives: http://www.analog.cx/docs/mailing.html#listarchives
> | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
> +------------------------------------------------------------------------
>
>

+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------

I was doing some experimentation and after reading the analog docs more
carefully, I realized that my syntax was wrong and I interchanged the '+'
and '-' in my G and g switches in the original command in the previous
emails.

It seems that I can run analog with an absolute path to a different config
file with the command:
/usr/local/analog-6.03/analog -G
+g/usr/local/analog-6.0.3/lib_analog_config/ob_analog.cfg

I verified this by executing it at different places within the directory
tree.



> -----Original Message-----
> From: analog-help-bounces@lists.meer.net
> [mailto:analog-help-bounces@lists.meer.net] On Behalf Of
> Richard Hamilton
> Sent: Friday, August 15, 2008 4:02 PM
> To: Support for analog web log analyzer
> Subject: Re: [analog-help] Alternate config files
>
> Brian,
>
> Just to avoid future confusion, what you have done there is
> actually to specify a relative path not an absolute path. You
> have launched analog from the analog-6.03 directory (thereby
> making it the present working
> directory) and have then specified lib_analog_config as the
> directory containing your config files, which is an immediate
> descendent of analog-6.03.
>
> The omission of the leading '/' is exactly what makes this a
> 'relative path'.
>
> R.
>
>
> Brian Clanton wrote:
> > AH!!
> >
> > Found my error.
> >
> > When I right crontabs I try to include absolute paths whenever
> > possible. It seems that I can invoke analog with an absolute path,
> > but from the
> > analog6.03 directory, I need to omit the "/" after the "-g"
> switch.
> > This is the command that works when I want to change config
> files and
> > want an absolute path declared for the analog executable:
> >
> > (The "glib" is not the gnu lib but -g and the directory
> "lib_analog_config"
> >
> > /usr/local/analog-6.03/analog +G -glib_analog_config/ob_analog.cfg
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: analog-help-bounces@lists.meer.net
> >> [mailto:analog-help-bounces@lists.meer.net] On Behalf Of Richard
> >> Hamilton
> >> Sent: Friday, August 15, 2008 3:19 PM
> >> To: Support for analog web log analyzer
> >> Subject: Re: [analog-help] Alternate config files
> >>
> >>
> >> Brian,
> >>
> >> "If the name of a configuration file given in a CONFIGFILE command
> >> doesn't include a directory, it will be looked for wherever analog
> >> expects to find its configuration files.
> >> (This location is a compile-time option.) For example, in
> the Windows
> >> version it would be in the same folder as the analog
> executable. This
> >> applies to the default and mandatory configuration files
> as well. But
> >> configuration files given with +g (***are relative to the current
> >> directory at the time you run the program***). "
> >>
> >> Perhaps absolute paths are therefore not supported?
> Assuming you are
> >> in Linux I suggest you try using the dot dot notation for
> the parent
> >> directory. For example:
> >>
> >> analog +G -g../lib_analog_config/alt_config.cfg
> >>
> >> assuming you have run the executable from
> >> /usr/local/analog-6.03/lib_analog_config/
> >>
> >> If you run it from ./analog-6.03/
> >>
> >> on the other hand then you would only need to use
> >> -g/lib_analog_config/alt_config.cfg
> >>
> >> Regards
> >> Richard
> >>
> >> Brian Clanton wrote:
> >>
> >>> I have an alternate config files that I want analog to use.
> >>>
> >>>
> >>> analog +G -galt_config.cfg
> >>>
> >>> However, I have multiple config files, so to keep it
> >>>
> >> organized, I have
> >>
> >>> a specific directory for them:
> >>>
> >>> /usr/local/analog-6.03/lib_analog_config
> >>>
> >>> I've tried using the directory path in the statement that
> >>>
> >> provides the
> >>
> >>> location of the config file, but it doesn't seem to work properly:
> >>>
> >>> analog +G
> -g/usr/local/analog-6.03/lib_analog_config/alt_config.cfg
> >>>
> >>>
> >>> What is the correct syntax to use to specify alternate
> >>>
> >> config files in
> >>
> >>> other directories?
> >>>
> >>>
> >>>
> >>
> +--------------------------------------------------------------------
> >> +-
> >>
> >>> +---
> >>> | TO UNSUBSCRIBE from this list:
> >>> | http://lists.meer.net/mailman/listinfo/analog-help
> >>> |
> >>> | Analog Documentation: http://analog.cx/docs/Readme.html List
> >>> | archives: http://www.analog.cx/docs/mailing.html#listarchives
> >>> | Usenet version:
> >>>
> >> news://news.gmane.org/gmane.comp.web.analog.general
> >>
> >>
> +--------------------------------------------------------------------
> >> +-
> >>
> >>> +---
> >>>
> >>>
> >>>
> >> +-------------------------------------------------------------
> >> ----------
> >> +-
> >> | TO UNSUBSCRIBE from this list:
> >> | http://lists.meer.net/mailman/listinfo/analog-help
> >> |
> >> | Analog Documentation: http://analog.cx/docs/Readme.html List
> >> | archives: http://www.analog.cx/docs/mailing.html#listarchives
> >> | Usenet version:
> >> | news://news.gmane.org/gmane.comp.web.analog.general
> >> +-------------------------------------------------------------
> >> ----------
> >> +-
> >>
> >>
> >
> >
> +---------------------------------------------------------------------
> > +---
> > | TO UNSUBSCRIBE from this list:
> > | http://lists.meer.net/mailman/listinfo/analog-help
> > |
> > | Analog Documentation: http://analog.cx/docs/Readme.html List
> > | archives: http://www.analog.cx/docs/mailing.html#listarchives
> > | Usenet version:
> news://news.gmane.org/gmane.comp.web.analog.general
> >
> +---------------------------------------------------------------------
> > +---
> >
> >
>
> +-------------------------------------------------------------
> ----------
> +-
> | TO UNSUBSCRIBE from this list:
> | http://lists.meer.net/mailman/listinfo/analog-help
> |
> | Analog Documentation: http://analog.cx/docs/Readme.html List
> | archives: http://www.analog.cx/docs/mailing.html#listarchives
> | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
> +-------------------------------------------------------------
> ----------
> +-
>

+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------