<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/16/16 12:51 PM, SoupNazi izaNpuoS
wrote:<br>
</div>
<blockquote
cite="mid:CADv1s40dPuTqVO9ybjrUiywwhmRax0L1rBGDV1SojLYpW=V4yg@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">Folks,
<div><br>
</div>
<div>It appears that there are some discrepancies between the
documentation (<a moz-do-not-send="true"
href="http://kea.isc.org/docs/kea-guide.html#logging">http://kea.isc.org/docs/kea-guide.html#logging</a>)
and the actual way the logging works in Kea.</div>
<div><br>
</div>
<div>I have been attempting to split off logging of kea-dhcp6 to
a separate log file. I have encountered some problems:</div>
<div><br>
</div>
<div>According to the documentation, the facility used is local0
by default. It doesn't seem to be. The facility as seen by
rsyslog on CentOS 7 is user.</div>
<div><br>
</div>
<div>Further, there appears to be no way to change the
facility. The documentation claims that you can use the <span>KEA_LOGGER_DESTINATION=</span><span>syslog[</span><span
class="gmail-optional">:<em class="gmail-replaceable"><code>fac</code></em></span><span>]</span><span> environment variable
to change the facility. This variable appears to only
changes the name of the daemon that did the logging. This
is the same behavior that the </span><span>output_options
under Logging{} does. </span></div>
<div><span><br>
</span></div>
<div><span>In order to successfully have good control over
logging while using syslog, we will need to have access to
changing the facility so that we can make it anything
local0-local7. That way we can setup specific log files for
certain aspects of the Kea DHCP server. </span></div>
<div><span><br>
</span></div>
<div><span>I am aware that with rsyslog, I can setup matches for
names where I could send all logs that contain "kea", for
example, to a specific file. Not all systems I manage run
rsyslog, however, as some run sysklogd where this is not
possible.</span></div>
<div><span><br>
</span></div>
<div><span>Is it on your radar to expose the ability to change
the logging facility in Kea in the future?</span></div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kea-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/kea-users">https://lists.isc.org/mailman/listinfo/kea-users</a>
</pre>
</blockquote>
<p><tt>Hi:</tt></p>
<p><tt><br>
Sorry for any inconvenience this is causing you, we already have
a ticket open for this:</tt></p>
<p><tt><a class="moz-txt-link-freetext" href="http://kea.isc.org/ticket/5053">http://kea.isc.org/ticket/5053</a></tt></p>
<p><tt>and it is scheduled to be included in our upcoming 1.2
release, which we are targetting for April/2017.</tt></p>
<p><tt>Thanks for reporting it, though. It always helps to have an
idea of how many people an issue may be affecting.</tt></p>
<p><tt><br>
</tt></p>
<p><tt>Sincerely,</tt></p>
<p><tt>Thomas Markwalder</tt></p>
<p><tt>ISC Software Engineering<br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt><br>
</tt></p>
</body>
</html>