I am still using a number of these boards in our test environment every
day. The fxp driver always complains but it hasn't stopped the nic from
working yet. I simply ignore the messages...
Bob
On Fri, Mar 09, 2001 at 10:23:21AM -0800, Mike Smith wrote:
> > What board is this?
>
> If this is t
Does anyone know if it is possible to use a cdr/cdrw
with 4.3 release? I want to use it with my sony vaio
f580 (notebook). I have the option of usb or pcmcia.
Can you tell me which models are known to work? Thanks
for your help. Please mail all responses to
[EMAIL PROTECTED] Thanks again.. Tom
_
hmmm i made all website files owned by apache owner and all was normal!
i told apc not to write to my webfiles yet it does anyways.
Anyone see anything fishy going on here?
On Thu, 12 Apr 2001, Dan Phoenix wrote:
> Date: Thu, 12 Apr 2001 14:25:46 -0700 (PDT)
> From: Dan Phoenix <[EMAIL PRO
:>:>scaleability.
:>:
:>:Uhm, that is actually not true.
:>:
:>:We keep namecache entries around as long as we can use them, and that
:>:generally means that recreating them is a rather expensive operation,
:>:involving creation of vnode and very likely a vm object again.
:>
:>The vnode ca
To update on this one box...
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
2399 bravenet2 0 17364K 15540K accept 0:00 1.07% 0.83% httpd
2401 bravenet2 0 20304K 18980K accept 0:00 1.01% 0.78% httpd
2446 bravenet2 0 16468K 14828K accept 0:
;
; APC ;
;
apc.cachedir="/usr/cache"
apc.relative_includes= 1
apc.check_mtime = 1
threw that in the php.ini file.
Started apache and booom webservers went to hell...each httpd taking
20 megs or more on a couple webservers. Anyone experience this?
Com
:Hello All,
:
:I am running a FreeBSD-4.2 NFS server with dozens of FreeBSD-4.2 NFS
:clients on 100BaseTX LAN. Recently I found that when the NFS server
:receives a lot of requests in a short period (e.g., 2 clients start X
:with gnome desktop simultaneously), all nfsd server processes hang in
:i
In message <[EMAIL PROTECTED]>, Matt Dillon writes:
>
>:
>:In message <[EMAIL PROTECTED]>, Matt Dillon writes:
>:
>:>Again, keep in mind that the namei cache is strictly throw-away, but
>:>entries can often be reconstituted later by the filesystem without I/O
>:>due to the VM Page cach
:
:In message <[EMAIL PROTECTED]>, Matt Dillon writes:
:
:>Again, keep in mind that the namei cache is strictly throw-away, but
:>entries can often be reconstituted later by the filesystem without I/O
:>due to the VM Page cache (and/or buffer cache depending on
:>vfs.vmiodirenable
In message <[EMAIL PROTECTED]>, Matt Dillon writes:
>Again, keep in mind that the namei cache is strictly throw-away, but
>entries can often be reconstituted later by the filesystem without I/O
>due to the VM Page cache (and/or buffer cache depending on
>vfs.vmiodirenable). So as
* Logan Gabriel <[EMAIL PROTECTED]> [010412 11:50] wrote:
> There is a hard to duplicate race condition in freebsd's
> kernel malloc. Bassically it is possiables for the kernel
> to tsleep way down in vm_page_sleep_busy even when M_NOWAIT
> is spefcied. Under some conditions this can block t
There is a hard to duplicate race condition in freebsd's
kernel malloc. Bassically it is possiables for the kernel
to tsleep way down in vm_page_sleep_busy even when M_NOWAIT
is spefcied. Under some conditions this can block the kernel
completly.
Attatched is a kernel module that demonstrat
On Thu, 12 Apr 2001, Matt Dillon wrote:
> Again, keep in mind that the namei cache is strictly throw-away,
This seems to be the main difference between Linux and FreeBSD.
In Linux, open files directly refer to an entry in the dentry
(and inode) cache, so we really need to have dynamically g
:You should also know that negative entries, since they have no
:objects to "hang from" and consequently would clog up the name-cache,
:are limited by the sysctl:
: debug.ncnegfactor: 16
:which means that max 1/16 of the name cache entries can be negative
:entries. You can monitor the numbe
In message <[EMAIL PROTECTED]>, Matt Dillon writes:
>
>:
>:On Tue, 10 Apr 2001, Matt Dillon wrote:
>:
>:>It's randomness that will kill performance. You know the old saying
>:>about caches: They only work if you get cache hits, otherwise
>:>they only slow things down.
>:
>:I wonder .
:
:On Tue, 10 Apr 2001, Matt Dillon wrote:
:
:>It's randomness that will kill performance. You know the old saying
:>about caches: They only work if you get cache hits, otherwise
:>they only slow things down.
:
:I wonder ... how does FreeBSD handle negative directory entries?
:
:Tha
Well, I am able to reproduce the crash pretty reliably, I don't know what is
causing it yet, I just kill all the other ypservs on a subnet except for this
one and it crashes about once every 5 minutes. I have some questions/theories
that I'd like to bounce off of people:
1) In the yp_all functi
On Tue, 10 Apr 2001, Matt Dillon wrote:
>It's randomness that will kill performance. You know the old saying
>about caches: They only work if you get cache hits, otherwise
>they only slow things down.
I wonder ... how does FreeBSD handle negative directory entries?
That is, /bin/s
See /usr/ports/audio/mpmf20. It's for MPMan F-20, might be helpful.
Regards, Markus.
On Wed, Apr 11, 2001 at 04:01:24PM +0200, Christoph Kukulies wrote:
> I'm seeking the header file in FreeBSD which corresponds to asm/io.h
> in Linux. It should contain macros like OUTPORT, INPORT etc.
> to do d
On Thu, Apr 12, 2001 at 07:52:39AM +, [EMAIL PROTECTED] wrote:
>
> Hi,
>
> I can't seem decipher the functionality of the accf_http.c file in the
> netinet directory ... I also couldn't find any documents that describe its
> purpose is it an HTTP filter or something like that ?
Have yo
Hi,
I can't seem decipher the functionality of the accf_http.c file in the
netinet directory ... I also couldn't find any documents that describe its
purpose is it an HTTP filter or something like that ?
Ashutosh S. Rajekar
http://www.rajekar.org
To Unsubscribe: send mail to [EMAIL PROTEC
21 matches
Mail list logo
