[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]

Re: logging of "loved" output

Bryan Stansell bryan@conserver.com
Wed, 22 Jun 2005 12:16:24 -0700 (PDT)

On Wed, Jun 22, 2005 at 02:18:15PM -0400, Kevin Korb wrote:
> I have played with the -U option a bit trying to get it to output to
> stdout with things like -U- but that didn't work.  I also discovered
> that -u and -U seem to handle CRLF translations differently which is a
> problem for me with -U.

yep, you have to give a filename to -U.  '-' isn't special - it'll just
create a file called '-'.

you shouldn't see any difference between the -u and -U output as far as
cr/lf are concerned...the code is writing the same data to each.  if you
end up seeing something, then it could be your tty doing translations of
that data when going to your terminal.

> I took a look into the source code and attempted to comment out the if
> command that prevents the logging of loved output but that didn't seem
> to help and the conserver code is a bit too convoluted for my limited
> knowledge of C.  Can anyone help with this?

check out lines 2644 and 2656 of conserver/group.c.  you'll see checks
for "pCEServing->pCLwr == (CONSCLIENT *)0".  remove those and -u will
output everything.

personally, i'd use -U with a filename and get the log parsing stuff to
just read from a file (lots of tools out there do that...gnu tail can
even do cool things to help).  or, even better, i'd be logging all the
console data to individual files and letting something like logsurfer do
it's magic to watch them all.  then you see *all* the data, instead of
the possibly-truncated info that -u/-U give you (yes, it truncates long
lines...because of the way it wants to output individual lines per
console, it has to buffer things to prevent madness on devices that
don't produce line-oriented output).

anyway, good luck - and hopefully something here helps.