On Fri, Apr 13, 2001 at 03:48:28PM -0600, Matt Simerson wrote:
Another thought is that this user may have had files still open. Even
if you "remove" a file, it really does not go away until the last open
handle is closed.
That seems like the most likely possibility. However, only one
Hi,
Can you check if this solves the drac problem in CURRENT ?
Does drac work the way it should ? There were some flags
actived in rpcgen, which shouldn't have been. I also modified
your port a bit to use tirpc code and to not include netdir.h
http://home.teleport.ch/freebsd/rpcgen.diff
Hi Anders,
As I have seen, drac can only handle IPv4 requests at the moment.
If you do like to see IPv6 support, I can make a patch for you.
We can now support Ipv6 with rpc ports, since tirpc supports
ipv6 also.
9001011udp6 :::0.0.0.0.3.225 - superuser
On Thu, Apr 12, 2001 at 02:24:36PM -0700, a little birdie told me
that Matt Dillon remarked
Without vmiodirenable turned on, any directory exceeding
vfs.maxmallocbufspace becomes extremely expensive to work with
O(N * diskIO). With vmiodirenable turned on huge directories
On Sat, Apr 14, 2001 at 09:34:26AM -0500, Matthew D. Fuller wrote:
On Thu, Apr 12, 2001 at 02:24:36PM -0700, a little birdie told me
that Matt Dillon remarked
Without vmiodirenable turned on, any directory exceeding
vfs.maxmallocbufspace becomes extremely expensive to work with
:Speaking of vmiodirenable, what are the issues with it that it's not
:enabled by default? ISTR that it's been in a while, and most people
:pointed at it have reported success with it, and it seems to have solved
:problems here and there for a number of people. What's keeping it from
:the
Sorry, posted it to -questions and -stable and no answer yet.
Maybe someone of you can help me
Hi there,
can someone tell me how/if file caching is done on freebsd over nfs?
are the parameters to modify the behaviour (e.g. memory usage)?
are there parameters for "normal" local disk cache also?
Wierdness in 4.2.
Scenario:
interface fxp0 has address 100.1.1.1. Use it with this address for awhile.
decide to change it to 100.1.1.5. do:
ifconfig fxp0 delete 100.1.1.1
ifconfig fxp0 100.1.1.5 netmask 255.255.255.0
viewing ifconfig shows the new address. HOWEVER, pinging 100.1.1.99, the
viewing ifconfig shows the new address. HOWEVER, pinging 100.1.1.99, the
freebsd machine sends out 100.1.1.1, the OLD address.
Is this cached/saved somewhere and not getting cleaned up?
in the routing table, apparently. If you do a "route -n get"
for the destination address you see the old
Bakul Shah wrote:
From the top level page I read hotmail handles 550,000 change
requests a day. Later in the article they say they have a
5000 server farm. That translates to 110 change requests a
day on average per server. If the peak rate is 10 times the
average, that is still only
10 matches
Mail list logo
