-
Notifications
You must be signed in to change notification settings - Fork 156
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
Logging to syslog even when set to syslog = off? #187
Labels
Comments
Let me take a look. |
dmatetelki
added a commit
that referenced
this issue
Oct 12, 2017
* Not turning on syslog when daemonizing (bugfix) * Making log-filename, recv-bufsize and send-bufsize parameters available though command line and mentioning them in the help (finishing incomplete feature)
Hi @stbc, The problem was that hitch turned logging to syslog on at daemonizing. |
dmatetelki
added a commit
that referenced
this issue
Oct 12, 2017
* Not turning on syslog when daemonizing (bugfix) * Making log-filename, recv-bufsize and send-bufsize parameters available though command line, config file and mentioning them in the help (finishing incomplete feature)
dmatetelki
added a commit
that referenced
this issue
Oct 20, 2017
* Not turning on syslog when daemonizing (bugfix) * Making log-filename, recv-bufsize and send-bufsize parameters available though command line, config file and mentioning them in the help (finishing incomplete feature)
dmatetelki
added a commit
that referenced
this issue
Oct 20, 2017
* Not turning on syslog when daemonizing (bugfix) * Making log-filename, recv-bufsize and send-bufsize parameters available though command line, config file and mentioning them in the help (finishing incomplete feature)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi everybody,
I got hitch running from the Debian backports repo. Although it states
syslog = off
in the hitch.conf, hitch still logs to syslog:
Is that a bug? Or it is supposed to be that way....?!
It would be nice to let hitch write those messages (and there are loads) to a separate log file
The text was updated successfully, but these errors were encountered: