On 08/29/2011 04:32 PM, Ionuț Arțăriși wrote:
> So if the auditlogging server is down, then the XMLRPC API is down. The
whole point of audit logging is to not let anything "important" pass
through without having a record of it. You can of course turn the
logging off from the server.
And someho
On Tue, Aug 23, 2011 at 06:26:18PM +0200, Bo Maryniuk wrote:
>
> The main core of the logger is a separate daemon that serves XML-RPC
> listener to a localhost only. Then each software component in the
> Spacewalk is going to send an logging event message through it.
Currently, every Spacewalk co
On Wed, Aug 24, 2011 at 01:49:27PM +0200, Bo Maryniuk wrote:
> On 08/24/2011 01:20 PM, Tomas Lestach wrote:
> >what was the original use/business case for the audit logging add-on?
> To know who did what, when and from where.
To achieve that, I'll gladly review a patch which will add logging
trigg
On Thu, Aug 25, 2011 at 02:30:51PM +0200, Johannes Renner wrote:
>
> Well, the general 'problem' is that Spacewalk consists of a lot of
> different components and this audit log should gather log events coming
> from these sources (web ui, frontend api, backend api, taskomatic),
> while sending th
On 08/30/2011 12:46 PM, Jan Pazdziora wrote:
I'd much rather see a patch which would [...] finish
the Perl-to-Java migration of the outstanding .pxt Web pages.
The topic is about Audit logging right now and you have your own
personal opinion on this. There will be always various ideas, of
cour
On Fri, Aug 26, 2011 at 04:10:03PM -0400, Cliff Perry wrote:
>
> Do you do it within the schema (and loose the who from where did what -
> unless all app code passes it down to DB).
No. You do it once, at the start of the HTTP request handling, store
that to the database and use identifier throug
On Tue, Aug 30, 2011 at 01:31:49PM +0200, Bo Maryniuk wrote:
> On 08/30/2011 12:46 PM, Jan Pazdziora wrote:
> >I'd much rather see a patch which would [...] finish
> >the Perl-to-Java migration of the outstanding .pxt Web pages.
>
> The topic is about Audit logging right now and you have your own
* Jan Pazdziora [Aug 30. 2011 12:07]:
>
> Currently, every Spacewalk component talks to one datastore, the
> underlying database. Why cannot that component log directly to the
> database to which it already has open connection, rather than trying
> to log to another daemon which might be down?
O
Ionuț Arțăriși wrote:
% Hello,
%
% I'm trying to reduce the amount of packages that own the same set of files.
%
% SputLite-server and SputLite-client both explicitly own
% /usr/lib/perl5/vendor_perl/5.10.0/NOCpulse/CommandQueue*
%
% Is this intentional or is it just a packaging bug? If it's a b
On Tue, Aug 30, 2011 at 01:51:49PM +0200, Klaus Kaempf wrote:
> * Jan Pazdziora [Aug 30. 2011 12:07]:
> >
> > Currently, every Spacewalk component talks to one datastore, the
> > underlying database. Why cannot that component log directly to the
> > database to which it already has open connectio
On 08/30/2011 02:14 PM, Jan Pazdziora wrote:
But Bo Maryniuk said in the initial post:
Q: Does it takes care of being tamper-proof?
A: No. The software component is responsible only to collect various
You cannot access it as a spacewalk admin.
--
Bo Maryniuk
SUSE LINUX Products GmbH, Maxfel
On 08/30/2011 12:06 PM, Jan Pazdziora wrote:
> To achieve that, I'll gladly review a patch which will add logging
> triggers to all tables that we have in the schema, together with
> initial insert to a central log table with identity/timestamp/remote
> host/user agent/whatever information.
How wo
On 08/30/2011 01:51 PM, Jan Pazdziora wrote:
Sure. I'm just pointing out that you might save yourself some
architecture and coding work if you consider the bigger picture and
goals of the project and not just blindly focus on the narrow goal you
have on your plate right now.
The narrow goal tha
On 08/29/2011 03:14 PM, Cliff Perry wrote:
In short, my personal preference is not to become a toaster if audit
logging has crashed (including out of space to write).
An alternative implementation we may consider for a second iteration is
to have Spacewalk send the messages via AMPQ to a broke
On Tue, Aug 30, 2011 at 05:29:48PM +0200, Miroslav Suchý wrote:
> On 08/30/2011 12:06 PM, Jan Pazdziora wrote:
> > To achieve that, I'll gladly review a patch which will add logging
> > triggers to all tables that we have in the schema, together with
> > initial insert to a central log table with i
15 matches
Mail list logo
