[Top][All Lists]

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

Re: tee: write error

From: Bob Proulx
Subject: Re: tee: write error
Date: Tue, 18 Sep 2007 09:29:29 -0600
User-agent: Mutt/1.5.9i

Saurabh Gupta wrote:
> tee (coreutils) 4.5.3

As Eric said that is a very old version.  But 'tee' itself I would not
expect to be sensitive to version and even very old versions should
work.  The 'tee' program is not a very complicated program.

> I am not seeing any error messages in /var/log/messages & other files.

That is encouraging.

> Just for your information, this error only comes when my application runs
> fast with lot of display messages which i am redirecting through tee to log
> file. but size of log file formed is too small (2437014 bytes)

Again, please report exactly the commands used to produce the error
and the error output that was generated from it.

> How can i avoid this error? Is there any way to redirect in log just like
> tee.

Without information this is impossible to say.

The 'tee' program simply reads input and writes output to two
different places.  It uses the libc standard I/O library for this
purpose.  Any errors reported by the stdio routines are reported.  The
libc stdio routines simply use the read(2) and write(2) system calls
and any errors they encounter are reported.  Typical write errors
would be due to network failures when using network storage or disk
errors when using local storage.  Those should be accompanied by
errors reported by the kernel into the system log.

Since you are reporting that no errors are being logged to the system
log then the only other error that I can think of that would produce
that message would be a write on a closed file descriptor.  Example:

  echo | tee /dev/null >&-

Does that produce the same message for you?  This is just a guess but
if so then it means that there is a bug in your script which is
closing a file before all processes have finished writing to it.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]