Re: *printf(9) and PRINTF_BUFR_SIZE

2011-04-09 Thread dieterbsd
While working on other problems with *printf(9), log(9), etc. I stumbled upon: options PRINTF_BUFR_SIZE=128 # Prevent printf output being interspersed. Question 1: Am I correct in thinking that PRINTF_BUFR_SIZE is supposed to prevent this: ada2: 300.000MB/s transfuhub2: 3 ports with 3 r

Re: *printf(9) and PRINTF_BUFR_SIZE

2011-04-09 Thread Alexander Best
On Sat Apr 9 11, dieter...@engineer.com wrote: > While working on other problems with *printf(9), log(9), etc. > I stumbled upon: > > options PRINTF_BUFR_SIZE=128# Prevent printf output being > interspersed. > > Question 1: Am I correct in thinking that PRINTF_BUFR_SIZE is supposed > to p

Re: printf doesn't work from kernel modules

2010-11-22 Thread Dmitry Krivenok
Just tried dys_sysctl. It doesn't work as well. Below are the results I got: r...@olimpico-freebsd 22:04:17 /usr/share/examples/kld/dyn_sysctl # [0] uname -a FreeBSD olimpico-freebsd 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Nov 22 21:35:15 MSK 2010 r...@olimpico-freebsd:/usr/obj/usr/src/sys/GENERIC

Re: printf doesn't work from kernel modules

2010-11-22 Thread Garrett Cooper
On Mon, Nov 22, 2010 at 5:38 AM, Dmitry Krivenok wrote: > Hello Hackers, > Recently I installed 8.1 on my laptop and recompiled the kernel. > The system works fine, but I have a strange problem with my own > trivial kernel module. > I noticed that printf function doesn't produce any output (accord

Re: PRINTF, STDOUT

2006-11-30 Thread Daniel Eischen
On Thu, 30 Nov 2006, Christopher Olsen wrote: Hello, I've been tracing the printf function from the FreeBSD 6.x libc... I'm trying to figure out what mechanism transfers the data from the processes FILE to the system so it's written out to the screen... From my findings I get to a function __

Re: printf....!

2003-02-10 Thread Andrey Simonenko
On Sat, 8 Feb 2003 22:13:32 + (UTC) in lucky.freebsd.hackers, Auge Mike wrote: > Hi all, > > I was trying to know how "printf" works in FreeBSD... I hvae reached to this > point : > > #define _write(fd, s, n) \ >__syscall(SYS_write, (int)(fd), (const void *)(s), (size_t)(n)) > > I'a

Re: printf()

2000-11-11 Thread Warner Losh
In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes: : printf("foo do foo\n"); : crash_here(); : printf("after the crash\n"); : : And never see the statement "foo do foo\n"; : Is that correct? Yes. But I had a lot of printfs in the code that I was debugging and the last few wouldn't be prin

Re: printf()

2000-11-11 Thread opentrax
On 10 Nov, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Zhenhai >Duan writes: > : Does the kernel function printf() flushes the output immediately, or it is > : possible some data is buffered somewhere and gets lost without printing > : to the console? like the corresponding funtion in t

Re: printf()

2000-11-11 Thread opentrax
On 10 Nov, Terry Lambert wrote: >> A simple question: >> >> Does the kernel function printf() flushes the output immediately, or it is >> possible some data is buffered somewhere and gets lost without printing >> to the console? like the corresponding funtion in the c library. > > There is no

Re: printf()

2000-11-10 Thread Warner Losh
In message <[EMAIL PROTECTED]> Zhenhai Duan writes: : Does the kernel function printf() flushes the output immediately, or it is : possible some data is buffered somewhere and gets lost without printing : to the console? like the corresponding funtion in the c library. Yes. It can be buffered,

Re: printf()

2000-11-10 Thread Terry Lambert
> A simple question: > > Does the kernel function printf() flushes the output immediately, or it is > possible some data is buffered somewhere and gets lost without printing > to the console? like the corresponding funtion in the c library. There is no buffering comparable to that of the stdio p

Re: printf()

2000-11-10 Thread Zhenhai Duan
Thanks for all of your replies. The reason I asked this question is that I really saw some incomplete print out on FreeBSD 3.3. My intuition is that the printout is buffered some where, otherwise, I would expect either there is a complete printout, or no printout at all. --Zhenhai On Fri, 10 Nov

Re: printf()

2000-11-10 Thread Mike Smith
> On 10 Nov, Mike Smith wrote: > >> > >> Is there is way that I could perhaps demonstrate my reasoning, > >> such that it might be satisfactory to you? > > > > No. > > > Then, should I take it you concede the point? No. -- ... every activity meets with opposition, everyone who acts has his r

Re: printf()

2000-11-10 Thread opentrax
On 10 Nov, Mike Smith wrote: >> >> Is there is way that I could perhaps demonstrate my reasoning, >> such that it might be satisfactory to you? > > No. > Then, should I take it you concede the point? Jessem. To Unsubscribe: send mail to [EMAIL PROTECTED]

Re: printf()

2000-11-10 Thread Dag-Erling Smorgrav
[EMAIL PROTECTED] writes: > [...] > Jessem. Amazing what people will do to evade killfiles. Plonk. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Re: printf()

2000-11-10 Thread Mike Smith
> > Is there is way that I could perhaps demonstrate my reasoning, > such that it might be satisfactory to you? No. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the t

Re: printf()

2000-11-10 Thread opentrax
On 10 Nov, Mike Smith wrote: >> >> Does the kernel function printf() flushes the output immediately, or it is >> >> possible some data is buffered somewhere and gets lost without printing >> >> to the console? like the corresponding funtion in the c library. >> > >> > It's not buffered afaik. >

Re: printf()

2000-11-10 Thread Mike Smith
> >> Does the kernel function printf() flushes the output immediately, or it is > >> possible some data is buffered somewhere and gets lost without printing > >> to the console? like the corresponding funtion in the c library. > > > > It's not buffered afaik. > > > Actually my experince in writi

Re: printf()

2000-11-10 Thread opentrax
On 9 Nov, Alfred Perlstein wrote: > * Zhenhai Duan <[EMAIL PROTECTED]> [001109 21:09] wrote: >> A simple question: >> >> Does the kernel function printf() flushes the output immediately, or it is >> possible some data is buffered somewhere and gets lost without printing >> to the console? like

Re: printf()

2000-11-09 Thread Alfred Perlstein
* Zhenhai Duan <[EMAIL PROTECTED]> [001109 21:09] wrote: > A simple question: > > Does the kernel function printf() flushes the output immediately, or it is > possible some data is buffered somewhere and gets lost without printing > to the console? like the corresponding funtion in the c library.

Re: printf() from KLD

1999-12-09 Thread Mike Smith
> This message was sent from Geocrawler.com by "Alex" <[EMAIL PROTECTED]> > Be sure to reply to that address. > > Hello, > > I use printf() function from my KLD for > debugging. Always, when the kernel call printf, I > see two same line, like : > Dec 9 15:40:10 techno /kernel: > Dec 9 15:40:1

Re: printf() from KLD

1999-12-09 Thread Archie Cobbs
Alex writes: > This message was sent from Geocrawler.com by "Alex" <[EMAIL PROTECTED]> > Be sure to reply to that address. > > Hello, > > I use printf() function from my KLD for > debugging. Always, when the kernel call printf, I > see two same line, like : > Dec 9 15:40:10 techno /kernel: >