Re: syslog

2004-01-03 Thread Dan Nelson
In the last episode (Jan 04), Eugene Grosbein said: > [EMAIL PROTECTED] wrote 8 years ago in src/lib/libc/gen/syslog.c: > > p += sprintf(p, "%.15s ", ctime(&now) + 4); > > What is '+ 4' for? ctime returns a date in the format: Thu Nov 24 18:22:48 1986\n\0 The +4 skips the day name. --

Re: syslog

2004-01-03 Thread Edwin Groothuis
On Sun, Jan 04, 2004 at 02:15:18AM +0700, Eugene Grosbein wrote: > Hi! > > [EMAIL PROTECTED] wrote 8 years ago in src/lib/libc/gen/syslog.c: > > p += sprintf(p, "%.15s ", ctime(&now) + 4); > > What is '+ 4' for? ctime() returns: Thu Nov 24 18:22:48 1986\n\0 So ctime()+4 returns:

Re: syslog

2004-01-03 Thread Eugene Grosbein
Eugene Grosbein wrote: > [EMAIL PROTECTED] wrote 8 years ago in src/lib/libc/gen/syslog.c: > > p += sprintf(p, "%.15s ", ctime(&now) + 4); > > What is '+ 4' for? Oh, I've got it. Please ignore this question, sorry. Eugene ___ [EMAIL PROTECTED] maili

syslog

2004-01-03 Thread Eugene Grosbein
Hi! [EMAIL PROTECTED] wrote 8 years ago in src/lib/libc/gen/syslog.c: p += sprintf(p, "%.15s ", ctime(&now) + 4); What is '+ 4' for? http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/gen/syslog.c.diff?r1=1.2&r2=1.3 Eugene Grosbein P.S. Please CC me, I'm not in list __

ng_ksocket ACCEPT lock related problem.

2004-01-03 Thread takawata
Hi, I noticed ng_ksocket can listen for stream type connection and wrote a test program like this, and it works as I expected, but it also produced LoR problem etc. Is this known problem? ===Message malloc() of "16" with the following non-sleepable locks held: exclusive sleep mutex inp (tcpinp) r

Re: Power Patches

2004-01-03 Thread Norikatsu Shigemura
On Thu, 01 Jan 2004 23:30:09 -0700 (MST) "M. Warner Losh" <[EMAIL PROTECTED]> wrote: > You should try it if: > 1) You are using hw.pci.unsupported_io=1. Turn it off and use > these patches. Let me know if it doesn't. Typically it > appears that this helps people hitting t

Re: [PATCH] sendfile erroniously returns ENOTCONN.

2004-01-03 Thread David G. Lawrence
> >Yes, I think checking for SS_CATSENDMORE (and returning EPIPE) prior to > > checking SS_ISCONNECTED (and returning ENOTCONN as it does now) is the right > > thing to do. > > Last question (I hope)... :) > > Why not call sosend? sosend is the primary mechanism that write(8) uses to send

Re: [PATCH] sendfile erroniously returns ENOTCONN.

2004-01-03 Thread David G. Lawrence
> * David G. Lawrence <[EMAIL PROTECTED]> [040102 21:41] wrote: > > > >sendfile(8) tries to maintain compatibility with sosend as much as is > > reasonable. ENOTCONN is the appropriate error to return if the socket > > isn't connected. sosend checks SS_CANTSENDMORE prior to the check for > > S

Re: [PATCH] sendfile erroniously returns ENOTCONN.

2004-01-03 Thread David G. Lawrence
> sendfile(2) returns ENOTCONN when the remote side has disconnected instead > of EPIPE. Can this fix be applied? Is there a reason for it being the > way it is? I know EPIPE can cause SIGPIPE which can cause problems, but > the error here is incorrect, and considering that the manpage mentions

Re: [PATCH] sendfile erroniously returns ENOTCONN.

2004-01-03 Thread Alfred Perlstein
* David G. Lawrence <[EMAIL PROTECTED]> [040103 00:55] wrote: > > * David G. Lawrence <[EMAIL PROTECTED]> [040102 21:41] wrote: > > > > > >sendfile(8) tries to maintain compatibility with sosend as much as is > > > reasonable. ENOTCONN is the appropriate error to return if the socket > > > isn