-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/12/2007 01:01 PM, Ralf Hildebrandt wrote:
> The upgrade from 2.01.10-31 to 2.01.10-32 broke my analysis scripts:
>
> grep -h "/anatomie/" /var/log/apache2/access.log.1
> /var/log/apache2/access.log |
> webalizer -p -o /var/www/anatomie/webalizer
> grep -h "/qualitaetsmanagement/" /var/log/apache2/access.log.1
> /var/log/apache2/access.log |
> webalizer -p -o /var/www/qualitaetsmanagement/webalizer
>
> etc.
That's really strange. I just did a few tests both in sarge
(using 2.01.10-26) and in etch (using 2.01.10-32) and the above lines
doesn't work as expected unless you force STDIN as documented in the
man page using '-'.
I would expected at least an error message from webalizer.
> webalizer was not generating ANY updated output after the upgrade from
> 2.01.10-31 to 2.01.10-32! Reverting back to 2.01.10-26 from stable made
> things work again.
I tested the lines above and here what happened:
$ grep -h "/~temp/" access.log.1 access.log |webalizer -p -o tmp/
Webalizer V2.01-10 (Linux 2.6.18-3-686) locale: en_US.UTF-8
Error: Can't open log file /var/log/apache2/access.log.1
Please, note that it will use the conf file and try to read
the indicated log file, once I changed the command line to:
$ grep -h "/~temp/" access.log.1 access.log |webalizer -p -o tmp/ -
It works as expected. I couldn't reproduce the behaviour you
pointed out, I would ask you to test with the '-' to force the STDIN.
[...]
Kind regards,
- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF08BOCjAO0JDlykYRApKBAJ9IA8Z2cySLQPgohUplhk81fPT3dgCfRK3L
RNdG57/xTwjivL6vxfWEktc=
=/xRI
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
