But of all the solutions here, I think it would be easier for us to just
reuse rhnServerAction and that infrastructure.. Config* stuff is built
in ... We could probably reuse the Event History UI to do the
failed/pending actions/ rescheduling, all that is built in. Its almost
like 1
I dunno if its the longest but changing the base channel for a System
used to take ~30 secs per system.. So if the user asked the base channel
to be changed for 100 systems its almost 50 min to get that done easily
timing out the request..
Partha
Miroslav Suchý wrote:
Jason Dobies wrote:
As
On Wed, Jan 28, 2009 at 5:43 AM, Miroslav Suchý msu...@redhat.com wrote:
Jason Dobies wrote:
As I was working on the performance enhancements for the SSM bulk
channel subscription change
(https://bugzilla.redhat.com/show_bug.cgi?id=469984) I started to wonder
if our approach to the SSM in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Jan 2009 09:48:42 -0500
Jesus M. Rodriguez jmro...@gmail.com wrote:
- - spacewalk-setup will prompt if you'd like an embedded
installation where we assume the admin doesn't know anything about
databases, then just yum install
On Wed, Jan 28, 2009 at 10:09 AM, Justin Sherrill jsher...@redhat.com wrote:
Jesus M. Rodriguez wrote:
On Tue, Jan 27, 2009 at 5:30 PM, Justin Sherrill jsher...@redhat.com wrote:
Jesus Rodriguez wrote:
On Tue, Jan 27, 2009 at 04:12:43PM -0500, Jason Dobies wrote:
[snip]
Outside of what we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looking for anyone who has experience with these particularly in the
realm of calling procedures, would love to bounce a few questions off
you.
It's looking like the Python DBAPI
(http://www.python.org/dev/peps/pep-0249/) method of calling stored
Devan Goodwin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looking for anyone who has experience with these particularly in the
realm of calling procedures, would love to bounce a few questions off
you.
It's looking like the Python DBAPI
(http://www.python.org/dev/peps/pep-0249/)
