Sponsored Content
Full Discussion: System Resources?
Top Forums UNIX for Advanced & Expert Users System Resources? Post 44528 by Perderabo on Monday 8th of December 2003 10:43:31 AM
Old 12-08-2003
I just do a setvbuf(stdout, NULL, _IONBF, 0) if I don't want buffering.

But I'm not sure that buffering per se is the issue here. The "lose valid data" does not strike me as the way to describe a delay in seeing the data. It may be that the OP has a bug that resulted in re-using the area already assigned as a buffer. When the buffer fills, the other data is trashed. If this is the case, turning off buffering may hide the symptom, but it does not fix the root problem.
 

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

VI hogging system resources???

Hello all. I was on my pc last night when I noticed that my hard drive light was on and when I typed in "uptime" I recieved some crazy load averages. load average: 3.30, 3.07, 2.95. Anyway I type in "top" to see what processes are being the resource hogs and im surprised as hell to see that one... (2 Replies)
Discussion started by: ThePreacher
2 Replies

2. UNIX for Advanced & Expert Users

Looking for utility to monitor system resources

Hi Community, I'm looking for a linux based utility for monitoring following system resources 1. Memory 2. CPU Usage I know there are plenty freewares which poll the data and print in form of html pages. For eg. MRTG, Novel's Linux Monitoring tools etc. But my requirement is deviated a... (1 Reply)
Discussion started by: anilgurwara
1 Replies

3. Ubuntu

Xorg is taking System Resources.

Hi All, I am facing System Speed problem.i saw in top command Xorg process was taking most of the time 20% of CPU and Memory.How to make it normal. Currently i am using AMD Athlon 64 HT technology processor(Socket 939) 512 DDR1 RAM Nvidia 5200 GeForce 128 MB Graphic card. i need help in... (2 Replies)
Discussion started by: arvindk.monu
2 Replies
SETBUF(3)						   BSD Library Functions Manual 						 SETBUF(3)

NAME
setbuf, setbuffer, setlinebuf, setvbuf -- stream buffering operations LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <stdio.h> void setbuf(FILE * restrict stream, char * restrict buf); void setbuffer(FILE *stream, char *buf, int size); int setlinebuf(FILE *stream); int setvbuf(FILE * restrict stream, char * restrict buf, int mode, size_t size); DESCRIPTION
The three types of buffering available are unbuffered, block buffered, and line buffered. When an output stream is unbuffered, information appears on the destination file or terminal as soon as written; when it is block buffered many characters are saved up and written as a block; when it is line buffered characters are saved up until a newline is output or input is read from any stream attached to a terminal device (typically stdin). The function fflush(3) may be used to force the block out early. (See fclose(3).) Normally all files are block buffered. When the first I/O operation occurs on a file, malloc(3) is called, and an optimally-sized buffer is obtained. If a stream refers to a terminal (as stdout normally does) it is line buffered. The standard error stream stderr is always unbuffered. Note that these defaults may be altered using the stdbuf(1) utility. The setvbuf() function may be used to alter the buffering behavior of a stream. The mode argument must be one of the following three macros: _IONBF unbuffered _IOLBF line buffered _IOFBF fully buffered The size argument may be given as zero to obtain deferred optimal-size buffer allocation as usual. If it is not zero, then except for unbuffered files, the buf argument should point to a buffer at least size bytes long; this buffer will be used instead of the current buffer. If buf is not NULL, it is the caller's responsibility to free(3) this buffer after closing the stream. (If the size argument is not zero but buf is NULL, a buffer of the given size will be allocated immediately, and released on close. This is an extension to ANSI C; portable code should use a size of 0 with any NULL buffer.) The setvbuf() function may be used at any time, but may have peculiar side effects (such as discarding input or flushing output) if the stream is ``active''. Portable applications should call it only once on any given stream, and before any I/O is performed. The other three calls are, in effect, simply aliases for calls to setvbuf(). Except for the lack of a return value, the setbuf() function is exactly equivalent to the call setvbuf(stream, buf, buf ? _IOFBF : _IONBF, BUFSIZ); The setbuffer() function is the same, except that the size of the buffer is up to the caller, rather than being determined by the default BUFSIZ. The setlinebuf() function is exactly equivalent to the call: setvbuf(stream, (char *)NULL, _IOLBF, 0); RETURN VALUES
The setvbuf() function returns 0 on success, or EOF if the request cannot be honored (note that the stream is still functional in this case). The setlinebuf() function returns what the equivalent setvbuf() would have returned. SEE ALSO
stdbuf(1), fclose(3), fopen(3), fread(3), malloc(3), printf(3), puts(3) STANDARDS
The setbuf() and setvbuf() functions conform to ISO/IEC 9899:1990 (``ISO C90''). BUGS
setbuf() usually uses a suboptimal buffer size and should be avoided. BSD
February 18, 2013 BSD
All times are GMT -4. The time now is 07:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy