%traceback section in config file?
Michael DeHaan
mdehaan at redhat.com
Wed Jan 28 16:11:02 UTC 2009
James Laska wrote:
> On Tue, 2009-01-27 at 17:10 -0500, Michael DeHaan wrote:
>
>
>> I also want to do a better remote status implementation, so I can say
>> "show me all my systems that are installing in my lab/datacenter and
>> what's up with them". Right now we have that, but it's based on their
>> start time and whether they've finished. Spacewalk has another
>> implementation that provides more granularity, I used to have a
>> mod_python filter handler one (before various API things broke it,
>> and
>> it was unreliable anyway), but maybe I'll rewrite it someday.
>>
>
> I'm anxious for your input here. I'm not yet sure of the best method to
> plug anamon (anaconda monitor) into this.
>
Wasn't planning to use it for that, since log parsing for all the
systems could be slow and error prone.
I need to find out the proper mod_python way to monitor gets to files
under a specific path.
The filter handler I was using before seems too intrusive.
>
>> Anyhow, I think tracebacks would be nice, but then again a failure in
>> post doesn't trigger a traceback, so it's not that common either.
>>
>
> Among lots of other files in /tmp, the anaconda monitoring code will
> send back a /tmp/anacdump.txt if encountered by your installing system.
>
Nice!
> Thanks,
> James
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
More information about the Kickstart-list
mailing list