-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
running goaccess from cron #41
Comments
Ruslan, how are you running goaccess from the cron? Also make sure On Wed, Oct 2, 2013 at 4:53 PM, Ruslan Keba notifications@github.com wrote:
|
@rukeba , make sure you use absolute paths inside cron. best, |
@allinurl, I am running goaccess from the cron like this:
The ~/.goaccessrc exists and it contains custom log format (%T added). |
@abgit thank you! i will check it. |
@rukeba, as @abgit said, check your paths. If running
shows request times, then running it through the cron should do the same thing. You can also try using Let me know how that goes. Thanks! On Thu, Oct 3, 2013 at 4:54 AM, Ruslan Keba notifications@github.com wrote:
|
@rukeba @allinurl , i have already a goaccess executed inside cron. Anyway, i have post a issue about a problem when goaccess is used inside sh -c. goaccess tries to automagically detect if output ">" is used in command line based on isatty(). The problem is that isatty() don't detect ">" when goaccess is invoked inside a sh -c as string. I think it's better to make goaccess export only when defined explicity by command line, eg: best, |
Thank you, @allinurl, @abgit for suggestions! You were right, the issue was in paths. I fixed goaccess path to absolute path and explicitly set path to config with -p option. Now all works like a charm. |
That's great! Closing this issue. |
Looks like goaccess do not see ~/.goaccessrc when running from cron.
I feel it is not goaccess problem, but rather cron.
May be you can help?
Thank you!
The text was updated successfully, but these errors were encountered: