[email protected] wrote:
Maybe I am challenged today - I don't know.  I extracted the files in my
directory.

Then:
[r...@mail spamdyke]# chmod +x /etc/spamdyke/spamdyke-stats

Since my Spamdyke logs are in /var/log/qmail/smtp/ I sent this command:
[r...@mail spamdyke]# cat /var/log/qmail/smtp/current | egrep -i -e "(^Feb
23 )" | /etc/spamdyke/spamdyke-stats

I get this in return:

[r...@mail spamdyke]# cat /var/log/qmail/smtp/current | egrep -i -e "(^Feb
23 )" | /etc/spamdyke/spamdyke-stats
Missing right curly or square bracket at /etc/spamdyke/spamdyke-stats line
185, at end of line
syntax error at /etc/spamdyke/spamdyke-stats line 185, at EOF
Execution of /etc/spamdyke/spamdyke-stats aborted due to compilation
errors (#1)
    (F) The lexer counted more opening curly or square brackets than closing
    ones.  As a general rule, you'll find it's missing near the place you
    were last editing.

Uncaught exception from user code:
        Missing right curly or square bracket at
/etc/spamdyke/spamdyke-stats line 185, at end of line
syntax error at /etc/spamdyke/spamdyke-stats line 185, at EOF
Execution of /etc/spamdyke/spamdyke-stats aborted due to compilation errors.
 at /etc/spamdyke/spamdyke-stats line 185


What did I do to it???

Sorry, it was me. I missed a right curly bracket ('}') at about line 98 when I was copying it.

I corrected it and tested it before attaching it this time.


Brent


Attachment: spamdyke-stats-scripts.tar.gz
Description: GNU Zip compressed data

---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
    Vickers Consulting Group offers Qmailtoaster support and installations.
      If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
     Please visit qmailtoaster.com for the latest news, updates, and packages.
     
      To unsubscribe, e-mail: [email protected]
     For additional commands, e-mail: [email protected]

Reply via email to