Re: abt Compaq Smart Array 642 (well HP really)

2003-07-13 Thread Ivajlo Nikolov
Well, This is not good. Cause I'm going to build a heavy load web (apache + mysql) server At this moment I can change the configuration of the server and ask for differnet SCSI RAID device enough tested and capable with STABLE. But I'm afraid in several days it will be later. Any s

Re: Running ethereal on FBSD

2003-07-13 Thread David Fleck
On Mon, 14 Jul 2003, Paul Civati wrote: > You will need to do this as root, what does -D actually do? ethereal man page: Network interface names should match one of the names listed in "tethereal -D". tethereal man page: -D Print a list of the interfaces on which Tethereal can ca

Re: cvs commit: src/sys/netipsec ipsec.c key.c

2003-07-13 Thread Mike Tancsa
Hi all, I have been seeing memory allocation errors on a few FreeBSD boxes running IPSEC. Does anyone know if the commit below addresses such a problem ? Or is this a racoon issue ? I did a search on google and have not seen anyone else mention this particular issue. Jul 14 00:57:57 d1terA9 ra

Re: Running ethereal on FBSD

2003-07-13 Thread Paul Civati
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (David Fleck) writes: > When I try to find out what interfaces it can capture data from, I get > this: > > dcf>$ tethereal -D > tethereal: There are no interfaces on which a capture can be done > > I've tried as root, same response. You

Running ethereal on FBSD

2003-07-13 Thread David Fleck
I'm trying to get ethereal running on my 4.6.2-RELEASE system. When I try to find out what interfaces it can capture data from, I get this: dcf>$ tethereal -D tethereal: There are no interfaces on which a capture can be done I've tried as root, same response. Now, the network's up and running wh

Promise PDC20378 SATA150 controller problems

2003-07-13 Thread Marcus Larsson
Hi all! According to www.freebsd.org/releases/5.1R/hardware-i386.html#AEN63 FreeBSD doesnt seem to support the PDC20378 chipset. Anyway, output of dmesg, atapci0: port 0xdc00-0xdc7f,0xdfa0-0xdfaf,0xdf00-0xdf3f mem 0xfeac-0xfead,0xfeafe000-0xfeafefff irq 11 at device 4.0 on

Re: usb.ko is unloadable?

2003-07-13 Thread Dmitry Morozovsky
On Sat, 12 Jul 2003, Dmitry Morozovsky wrote: DM> that this process is much complicated by the fact usb.ko module can not be DM> unloaded 'cause some process is referencing it: DM> DM> [EMAIL PROTECTED]:~/tmp> kldstat -v -i 11 DM> Id Refs AddressSize Name DM> 111 0xc0cf7000 1b000us

sshd 'zombie' processes

2003-07-13 Thread M. Warner Losh
each scp or ssh I do to a 4.8-stable machine I have gives me two 'zombie' processes: root 282 0.0 0.4 5236 2184 ?? I 7:41AM 0:00.05 sshd: imp [priv] (sshd) imp 284 0.0 0.4 5252 2260 ?? I 7:41AM 0:00.01 sshd: [EMAIL PROTECTED] (sshd) I had been running 4.8-RC when I

Re: sys/dev/ie/if_ie.c warnigns in yesterdays CVSup

2003-07-13 Thread Kris Kennaway
On Sun, Jul 13, 2003 at 12:03:07PM +0300, Pekka Savola wrote: > Hi, > > I'm not sure if this has been brought up in the past yet, but when > building the kernel from yesterdays 4_RELENG CVSup, I got a lot of > complilation warnings (it seems if_ie.c hasn't been updated in 3 months, > so changes

sys/dev/ie/if_ie.c warnigns in yesterdays CVSup

2003-07-13 Thread Pekka Savola
Hi, I'm not sure if this has been brought up in the past yet, but when building the kernel from yesterdays 4_RELENG CVSup, I got a lot of complilation warnings (it seems if_ie.c hasn't been updated in 3 months, so changes have happened elsewhere, it seems.) HTH, /usr/src/sys/dev/ie/if_ie.c: I