<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sssd2.git/common/elapi/elapi_basic.h, branch maint-0.7</title>
<subtitle>System Security Services Daemon [okos' clone]</subtitle>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/'/>
<entry>
<title>ELAPI Compatibility code for getifaddr()</title>
<updated>2009-10-16T18:27:24+00:00</updated>
<author>
<name>Dmitri Pal</name>
<email>dpal@redhat.com</email>
</author>
<published>2009-10-07T13:45:39+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=01bf2fcf57944104f9a774c8716950f397d666ce'/>
<id>01bf2fcf57944104f9a774c8716950f397d666ce</id>
<content type='text'>
Addreses ticket #94
Actually works pretty well.
To try use --enable-compat when build ELAPI.
It will use compatibility code instead of
getifaddr().
The trick in the elapi_ioctl.h with memory
allocation is taken from Stevens book.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Addreses ticket #94
Actually works pretty well.
To try use --enable-compat when build ELAPI.
It will use compatibility code instead of
getifaddr().
The trick in the elapi_ioctl.h with memory
allocation is taken from Stevens book.
</pre>
</div>
</content>
</entry>
<entry>
<title>ELAPI Adding file provider and CSV format</title>
<updated>2009-09-08T23:26:27+00:00</updated>
<author>
<name>Dmitri Pal</name>
<email>dpal@redhat.com</email>
</author>
<published>2009-09-02T23:41:06+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/okos/public_git/sssd2.git/commit/?id=13cf6a9c9d37a14ff46f6d512aab402616359570'/>
<id>13cf6a9c9d37a14ff46f6d512aab402616359570</id>
<content type='text'>
This patch creates the infrastructure for
logging of the event from the top of the interface
to the bottom. It is a start. A lot of functionality
is left aside.
The attempt of this patch is pass event from caller
of the ELAPI interface via targets to sinks
then to providers and do serialization creating
entity that is ready to be written to a file.
It also implements more specific provider related
configuration parameters.
Also it addresses couple suggestions that were
brought up against previous patch.

ELAPI Correcting issues

This patch addresses the issues found during the
review of the previous patches and addresses
ticket #166.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch creates the infrastructure for
logging of the event from the top of the interface
to the bottom. It is a start. A lot of functionality
is left aside.
The attempt of this patch is pass event from caller
of the ELAPI interface via targets to sinks
then to providers and do serialization creating
entity that is ready to be written to a file.
It also implements more specific provider related
configuration parameters.
Also it addresses couple suggestions that were
brought up against previous patch.

ELAPI Correcting issues

This patch addresses the issues found during the
review of the previous patches and addresses
ticket #166.
</pre>
</div>
</content>
</entry>
</feed>
