I am upgrading from analog 4.13 to the latest version 5.31. I am running
analog on an HP/Compaq alpha with OS Tru64 UNIX 5.1a. Under version 4.13 I
would specify the LOGFILES using a wildcard, e.g.
LOGFILE /var/log/httpd/y2k.maths.ox.ac.uk/access.log*
which worked a treat. However under version
Hello,
Although I don't have a solution for this, it may be
helpful for Stephen to know that this bug does not
effect Tru64 prior to version 5. I have used this
successfully many times on Tru64 4.0 without issue.
As far as the DNS resolution goes, I've never used
built-in DNS resolution that
I'm a bit confused here. But did you compile analog yourself? Did you
specify
NODIRENT when you compiled it?
No, I used a version compiled by my webmaster. The error was that she named
'analog' an old version (v.1.19 ?) and named 'analog3' a newer version, then
I was using an old version that
On Fri, 12 Mar 1999, Jim Sander wrote:
***CLUE:
If I select only one file, it works perfectly:
LOGFILE /usr/home/netmk/www_logs/www.990303
This is a wild guess, but check to make sure your shell is set to
expand wildcards. (you can usually turn this off with 'noglob') How about
if
I'm a bit confused here. But did you compile analog yourself? Did you specify
NODIRENT when you compiled it?
--
Stephen Turner[EMAIL PROTECTED]http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
"Ad infinitum, if not ad nauseam."
***CLUE:
If I select only one file, it works perfectly:
LOGFILE /usr/home/netmk/www_logs/www.990303
This is a wild guess, but check to make sure your shell is set to
expand wildcards. (you can usually turn this off with 'noglob') How about
if you do an `ls -l www.99*` - does that work?
I'm having troubles with wildcars on LOGFILE command.
I've a directory with diferent log files:
www.990301.gz, www.990302, www.990303, www.990304
www.990305.gz, www.990306, www.990307, www.990228
If I select only one file, it works perfectly:
LOGFILE /usr/home/netmk/www_logs/www.990303
But
