Re: why lighttpd complain sendfile: Broken pipe 32

2007-12-12 Thread Stefan Lambrev
Hi Ken, Ken Chen wrote: What causes this happen? 2007-12-12 21:17:47: (network_freebsd_sendfile.c.173) sendfile: Broken pipe 32 2007-12-12 21:17:47: (connections.c.603) connection closed: write failed on fd 149 2007-12-12 21:19:19: (network_freebsd_sendfile.c.173) sendfile: Broken pipe 32

why lighttpd complain sendfile: Broken pipe 32

2007-12-12 Thread Ken Chen
What causes this happen? 2007-12-12 21:17:47: (network_freebsd_sendfile.c.173) sendfile: Broken pipe 32 2007-12-12 21:17:47: (connections.c.603) connection closed: write failed on fd 149 2007-12-12 21:19:19: (network_freebsd_sendfile.c.173) sendfile: Broken pipe 32 2007-12-12 21:19:19:

Re: why lighttpd complain sendfile: Broken pipe 32

2007-12-12 Thread Jeremy Chadwick
On Wed, Dec 12, 2007 at 03:58:43PM +0200, Stefan Lambrev wrote: 2007-12-12 21:20:30: (connections.c.603) connection closed: write failed on fd 158 This is probably because the client closed the connection before the server send all data - so broken pipe. And ideally the handler in

Re: More issues with 7.0-BETA4

2007-12-12 Thread Peter Jeremy
On Wed, Dec 12, 2007 at 12:36:23AM +, Hugo Silva wrote: Building 32 bit binaries on amd64 apparently isn't working: # cc -m64 -march=k8 -o test64 test.c ./test64 testing!! # cc -m32 -march=k8 -o test32 test.c ./test32 /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for

Re: G965 patch for 6.3-Beta

2007-12-12 Thread Hiroshi Nishida
Hi. Hiroyuki Une wrote: Ah, my box froze and Xorg.0.log wasn't created. Well, if you turn off soft-updates and use sync mode, it will be created. Xorg at least leaves messages beginning like: X.Org X Server 1.4.0 Release Date: 5 September 2007 Anyway, I have no idea. It may be due to

panic: ffs_blkfree: freeing free block on 7.0-PRE

2007-12-12 Thread Philipp Ost
Hi all, I just got a panic on my 7.0-PRERELEASE box. Here's the backtrace: # kgdb kernel.debug /var/crash/vmcore.0 [...] Unread portion of the kernel message buffer: handle_workitem_freeblocks: block count dev = ad4s1f, block = 7475968, fs = /usr panic: ffs_blkfree: freeing free block Uptime:

RELENG_7 vchans broken Maestro

2007-12-12 Thread Dominic Fandrey
Since the switch to BETA4 (it might actually have happened earlier and I didn't recognize) vchans don't work properly anymore (for me). Instead of hearing a second source there only gets a lot of noise mixed into the first audio stream. # uname -a FreeBSD homeKamikaze.norad 7.0-BETA4 FreeBSD

Re: panic: ffs_blkfree: freeing free block on 7.0-PRE

2007-12-12 Thread Pieter de Goeje
On Wednesday 12 December 2007, Philipp Ost wrote: Hi all, I just got a panic on my 7.0-PRERELEASE box. Here's the backtrace: # kgdb kernel.debug /var/crash/vmcore.0 [...] Unread portion of the kernel message buffer: handle_workitem_freeblocks: block count dev = ad4s1f, block = 7475968, fs

Re: RELENG_7 vchans broken Maestro

2007-12-12 Thread Ariff Abdullah
On Wed, 12 Dec 2007 22:33:47 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: Since the switch to BETA4 (it might actually have happened earlier and I didn't recognize) vchans don't work properly anymore (for me). Instead of hearing a second source there only gets a lot of noise mixed into the

Re: More issues with 7.0-BETA4

2007-12-12 Thread Hugo Silva
Peter Jeremy wrote: On Wed, Dec 12, 2007 at 12:36:23AM +, Hugo Silva wrote: Building 32 bit binaries on amd64 apparently isn't working: # cc -m64 -march=k8 -o test64 test.c ./test64 testing!! # cc -m32 -march=k8 -o test32 test.c ./test32 /usr/bin/ld: skipping incompatible

Server motherboard recommendation wanted

2007-12-12 Thread geek
I am going to build two identical file servers using FreeBSD. They will be in a mixed linux and windoze network. I intend to use SCSI drives. I am not looking for the latest and greatest. I am not looking for each and every possible bell and whistle. I DO want maximum stability, reliability