The warning message you are getting means that Analog didn't even parse your LOGFILE line(s), so you should look for other error messages, check to make sure the lines don't have '#' at the start, and possible run analog with "SETTINGS ON" to see how it's reading those lines.
Paths in Unix are very similar to Windows except the direction of the slash. Most likely, however, you are running Analog from a working directory that is not where it is installed. Log file names without a leading slash are relative to the working path, not the location of Analog or the config file. Your best bet is to use fully qualified path names, especially if you are planning to schedule this process. -- Jeremy Wadsack Seven Simple Machines -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Gumbrell Sent: Monday, November 14, 2005 4:18 PM To: [email protected] Subject: [analog-help] logfile path in Linux vs Windows Hi. I've been using Analog on my Windows machine for a couple of years but am now switching over to Linux, at which I am currently a complete dunce. I've downloaded the 6.0 source package and compiled it without editing the anlghead file. I copied my existing config file over and made some slight adjustments due to a new file structure, but can't get the program to run successfully. I get the error 'Warning D: LOGFORMAT in configuration file analog.cfg with no subsequent LOGFILE.' I do have customised logformat lines but they are before the logfile lines, and have never been a problem before. The only thing I've tried to adjust is the paths, but being new to Linux I don't quite understand how to specify these. The logs (named 'www.example.com.0.gz' thru '~6.gz') are stored in a subfolder /R4files off of the main Analog folder, and I generate a report from 7 days' worth at a time. So my logfile line I thought should be: LOGFILE R4files/www.example.com.0.gz,R4files/www.example.com.1.gz, etc. through to the seventh one. I also tried with an initial slash, and with a ./ but no joy. Of course in Windows I just started with R4files\www and used backslashes throughout but I presume that's not the case in Linux. Should I be specifying complete paths, i.e. /home/user/Analog/R4files/www. etc.? The only other remark in the error file is that it always fails to open the output file too, so I presume this is a paths-related issue, or permissions or something? Cheers, gumb. +----------------------------------------------------------------------- - | 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 +------------------------------------------------------------------------
