Redirecting Anaconda output

[Klaus Steden]

I could have sworn Dan Trainor said this Thu, Jun 23, 2005 at 07:12:55PM -0700 ...
> Klaus Steden wrote:
> >>Hello, Prasad, and thanks for the response -
> >>
> >>I am aware of the install.log, but I am loking for is a way to redirect
> >>Anaconda's messages during the actuall install, or attempt to install, so
> >>that I can debug failed installs.
> >>
> > 
> > I have to say that that wouldn't suck, as an option.
> > 
> >>From what I've seen looking through the anaconda source code, it wouldn't
> >>be too difficult to implement, at least the C portion.
> > 
> > Klaus
> > 
> 
> Wonder if I can write something to broadcast over syslog to another machine.
> 
In which language? I only know the C one well - although I'd be willing to
surmise that the Python approach (like everything else Python) is easy.
>
> Do you think you'd be able to write this in C?  I'm sure others would be
> interested in this.
> 
I think I could, although right now I'm way short on time due to work demands.

The C API for syslog is fairly straightforward, and is part of libc ...
however, the client side of it is pretty dumb and it can only forward logging
messages to a remote syslogd if there is a local syslogd - since the daemon is
responsible for the forwarding, as instructed by /etc/syslog.conf.

An alternative approach may be to use the 'logger' shell command with the '-u'
switch, after initializing something to hand off data received from a local
Unix domain socket to a remote syslogd.

A better approach, imo, would be to incorporate functionality that the *BSD
people put in their 'logger' command - a '-h' switch that allows you to
specify a destination host.

In the end, syslog is simply a UDP message-passing framework with some
filtering logic on top. Shouldn't be too hard - but I know it'll be some weeks
before I can even entertain the idea.

What's everyone else out there think of the idea?

Klaus