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

log_file config should not be mandaroty #29

Closed
crosser opened this issue May 11, 2020 · 3 comments
Closed

log_file config should not be mandaroty #29

crosser opened this issue May 11, 2020 · 3 comments

Comments

@crosser
Copy link

crosser commented May 11, 2020

dhcpy6d allows logging via syslog, but when logging is enabled, it requires logfile to be specified, to be a regular file (disallowing /dev/null) and to be owned by the daemon.

On a production system, one typically uses syslog (possibly remote) for logging, and having a separate log file to take care of is an unnecessary complication.

I think that dhcpy6d should allow to configure logging via syslog only, and not require log file to be present or configured.

@HenriWahl
Copy link
Owner

HenriWahl commented May 13, 2020

You are absolutely right, makes sense not to require a log file. I will have a look for this.

@HenriWahl
Copy link
Owner

HenriWahl commented Jul 23, 2020

Please check the testing packages from https://dhcpy6d.ifw-dresden.de/download

@HenriWahl
Copy link
Owner

HenriWahl commented Jul 24, 2020

Fixed in latest release 1.0.1.

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

No branches or pull requests

2 participants