Re: logging of "loved" output

OK, I went back to my log file from when I was testing with -U and at
first it looks like what I described however when I dig into it with a
hex editor I can see what is happening...

When I was attached I saw:
[timestamp] [port]*: data\r\n

When I was NOT attached in I saw:
[timestamp] [port]: \rdata\r\n

This difference was probably just a tcsh vs syslog thing and not related
to conserver.

The first \r was overwriting the timestamp on my display and causing it
to dissapear.  The \r at the end was also getting truncated most of the
time do to the length of the lines causing the results to look even more
random.

I am going to stick with my current setup for now since using the
logfile option in the config file doesn't truncate the lines like -U and
-u did.

BTW, the I am not using conserver for the timestamping.  I have
timestamp set to "" in the config file and I am piping the output
through multilog (http://cr.yp.to/daemontools/multilog.html) to get
tai64n formatted timestamps instead which is why I wanted output to
stdout before.  Now I am getting that functionality by setting the
logfile to a named pipe that multilog is reading.

Not sure why the Linux consoles are putting in all those extra \r chars.

Thanks for the help.

--
Kevin

On Wed, 22 Jun 2005, Bryan Stansell wrote:

> Date: Wed, 22 Jun 2005 15:20:43 -0700
> From: Bryan Stansell <bryan@conserver.com>
> To: users@conserver.com
> Subject: Re: logging of "loved" output
>
> On Wed, Jun 22, 2005 at 03:37:48PM -0400, Kevin Korb wrote:
> > Those are different line numbers than what you said but the text looks
> > to be the same.  The patch didn't seem to have any effect.  All I get on
> > stdout is the login/logout messages with nothing in between.
>
> you zapped the wrong lines.  you want to keep the 'unloved' stuff and
> nuke the 'pCLwr' stuff.
>
> > There is a difference in how conserver treats CRLF between -u and -U
> > because when I run -Ufile I get 1 timestamp at the top and then never
> > get another one.  The only time -U logs timestamps is when I am actually
> > logged in.
>
> huh?  as i said, conserver doesn't do anything different between the two
> methods...they both output the same data.
>
> now, interpreting things a bit differently, based on hints above, it
> could be that file buffering is biting you.  stuff going to the file
> based on -U will, by default, be buffered to a block at a time...instead
> of line based or character based.  is *that* what's happening?  (all
> file output is that way, actually).
>
> what confuses me is you're saying things behave differently when you're
> logged in.  i'm not seeing that behavior.  if you could specify how to
> reproduce the problem, that would be good.
>
> your other message said the 'logfile' option helped.  that just sends
> stuff that would have been stdout/stderr to a file.  unless you hacked
> the -u code, you still wouldn't get output when users are attached.
>
> basically, i'm thoroughly confused.  i'm glad it's working for you, but
> i'm hoping that if there are issues, i can get more details and fix
> things.
>
> Bryan
> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users