Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for logging to a logfile #45

Open
GoogleCodeExporter opened this issue Apr 15, 2015 · 2 comments
Open

Add support for logging to a logfile #45

GoogleCodeExporter opened this issue Apr 15, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

R.E.Sonneveld@sonnection.nl:
"it would be nice if gross would log to the $BASE/log directory. E.g.
when having /usr/local/gross, log to /usr/local/gross/log/grossd.log."

I gave it a low priority for now as we already have syslog logging.

Original issue reported on code.google.com by eino.tuominen@gmail.com on 2 Feb 2007 at 10:05

@GoogleCodeExporter
Copy link
Author

I solved it by running gross with the -d switch, and starting it with a script 
that
redirects all output to a file. A cronjob runs to rotate the logfile at 
midnight by
catting all the contents to a timestamped file, and emptying the current 
logfile.

A cleaner log mechanism would still be appreciated though.

Original comment by aju...@gmail.com on 12 Feb 2008 at 12:25

@GoogleCodeExporter
Copy link
Author

Half way through. I have now implemented a new logging mechanism for logging 
queries. 

Format:
a=block d=558 w=5 c=130.232.202.134 s=eino@utu.fi r=eino@utu.fi h=smtp.utu.fi
m=zen.spamhaus.org+3 m=blocker+2

where
a = action
d = delay
w = total weight
c = client ip
s = sender
r = recipient
h = helo/ehlo
m = match from 

Original comment by eino.tuominen@gmail.com on 16 Apr 2008 at 6:03

  • Changed state: Started

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant