You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
I'm using the '-l' argument to tell barnyard2 where to write its own log. However, I never see any files being created or updated there. Documentation on barnyard's logging seems a bit sparse. What exactly is it supposed to write to its log?
I'm asking about this because barnyard2 has been crashing recently (database errors), and it would be nice to see relevant information in a log. Instead of that, I have to run barnyard2 from the command line and wait for it to crash again.
This is on Windows 8.1 64 bit.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using the '-l' argument to tell barnyard2 where to write its own log. However, I never see any files being created or updated there. Documentation on barnyard's logging seems a bit sparse. What exactly is it supposed to write to its log?
I'm asking about this because barnyard2 has been crashing recently (database errors), and it would be nice to see relevant information in a log. Instead of that, I have to run barnyard2 from the command line and wait for it to crash again.
This is on Windows 8.1 64 bit.
The text was updated successfully, but these errors were encountered: