Hi all,
In the BSD/OS there is a kernel countdown counter that can be used
to reboot the machine in case of lock. It´s called deadmantimer.
I used to put a cron entry to preset this counter every 3 min, so
if it goes to zero the server is rebooted.
In the past it save me
vladone [EMAIL PROTECTED] writes:
Recently i have in gateway freebsd that go down due to an DoS attack.
I dont know exactly what is (i dont have experience), but is useful if
someone, with more
wiyh more experience, can give some parameters for sysctl to prevent
Dos an flood problem
, can give some parameters for sysctl to prevent
Dos an flood problem.
Or perhaps with ipfw rules.
Any help will be apreciated!
The question is too general. Every resource that is consumed by
incoming traffic is potentially subject to a denial-of-service
attack.
Furthermore, most
Recently i have in gateway freebsd that go down due to an DoS attack.
I dont know exactly what is (i dont have experience), but is useful if someone,
with more
wiyh more experience, can give some parameters for sysctl to prevent
Dos an flood problem.
Or perhaps with ipfw rules.
Any help
Hello,
Sorry! I say syslog is not there but it is there with problems !!!
-bash-2.05b# /usr/sbin/syslogd
syslogd: child pid 39793 exited with return code 1
My System do not have Sysctl .. how can I bring sysctl to my system.
Sadashiv
___
freebsd
On 2005-06-23 20:45, Sadashiv Kulthe [EMAIL PROTECTED] wrote:
Hello,
Sorry! I say syslog is not there but it is there with problems !!!
-bash-2.05b# /usr/sbin/syslogd
syslogd: child pid 39793 exited with return code 1
My System do not have Sysctl .. how can I bring sysctl to my system
Please do your home work and read the man sysctl page before just
posting messages.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Sadashiv
Kulthe
Sent: Thursday, June 23, 2005 11:15 AM
To: freebsd-questions@freebsd.org
Subject: sysctl
Hello,
Sorry! I
fbsd_user wrote:
Please do your home work and read the man sysctl page before just
posting messages.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Sadashiv
Kulthe
Sent: Thursday, June 23, 2005 11:15 AM
To: freebsd-questions@freebsd.org
Subject: sysctl
on
my client connections, my firewalls are not running any servies only
firewall+router, them after checking the sysctl options:
test$ sysctl -a
I see some options:
net.inet.ip.portrange.lowfirst:1023
net.inet.ip.portrange.lowlast:600
net.inet.ip.portrange.first:1024
net.inet.ip.portrange.last:5000
perikillo wrote:
A) What is the meaning of fastforwarding, went is the best situation to use
this option?
B) Iam not running any services, them lowfirst and lowlast i think they
never go in action, them i can live with there default values?
C) Now the other values, wich values are the recomend
dear list,
I own a ath(4) card and would be interested in information about the the
meaning of these ath sysctl tueables.
Which can be changed? Which values can these changeable tuneables take?
hw.ath.hal.dma_brt: 2
hw.ath.hal.sw_brt: 10
hw.ath.hal.swba_backoff: 0
hw.ath.dwell: 200
dear list,
I own a ath(4) card and would be interested in information about the the
meaning of these ath sysctl tueables.
Which can be changed? Which values can these changeable tuneables take?
hw.ath.hal.dma_brt: 2
hw.ath.hal.sw_brt: 10
hw.ath.hal.swba_backoff: 0
hw.ath.dwell: 200
/ports/graphics/png
and give command make it gives following error
-bash-2.05b# pwd
/usr/ports/graphics/png
-bash-2.05b# make
/usr/sbin/sysctl: not found
/usr/ports/Mk/bsd.port.mk, line 1030: warning: /usr/sbin/sysctl -n
kern.osreldate returned non-zero status
I have virtual server from
sysctl?)
Thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-freebsd-
[EMAIL PROTECTED] On Behalf Of Luciano Musacchio
Sent: Sunday, March 06, 2005 3:05
To: freebsd-questions@freebsd.org
Subject: dma/sysctl
Hi,
I've a fbsd machine that hangs once in a while, I've this
en /var/log
the kernel to reboot on such cases?
(via sysctl?)
This is 5.3, right? I bet you would not have such
problems with 4.X.
My PC instantly crashed at boot with this same
message. I solved it by adding following to
/boot/loader.conf:
hw.ata.ata_dma=0
This will force the harddisk to operate in slow
PIO4
once in a while,
I've this en /var/log/messages:
...
Mar 5 14:44:58 chiba kernel: ad2: WARNING -
WRITE_DMA UDMA ICRC error (retrying request)
LBA=2949471
...
So, this means my hd is about to crash?
How can I tell the kernel to reboot on such cases?
(via sysctl?)
This is 5.3, right
Hello,
I searching for a list of sysctl variables.In handbook says that it's about
5000 of sysctl variables.I can find only 50 in the internet and handbook.Where
i can find a full list of sysctl variables?
Thanks.
___
[EMAIL PROTECTED] mailing list
I searching for a list of sysctl variables.In handbook says that it's about
5000 of sysctl variables.I can find only 50 in the internet and
handbook.Where i can find a full list of sysctl variables?
I don't know of a published magical list of all sysctl variables
because they are dependent
Hi Eric,
Friday, December 3, 2004, 8:55:38 PM, you thoughtfully wrote the following:
I searching for a list of sysctl variables.In handbook says
that it's about 5000 of sysctl variables.I can find only 50 in the
internet and handbook.Where i can find a full list of sysctl
variables?
I
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-freebsd-
[EMAIL PROTECTED] On Behalf Of Byte Byte
Sent: Saturday, December 04, 2004 0:42
To: [EMAIL PROTECTED]
Subject: List of sysctl variables
Hello,
I searching for a list of sysctl variables.In handbook says that it's
one could include -d option too, then you will get a short description
what each sysctl mean...
I didn't know about that option. Thanks!
--
If I write a signature, my emails will appear more personalised.
___
[EMAIL PROTECTED] mailing list
http
Dear users,
I recently upgraded my FreeBSD 4.10 tot FreeBSD 5.3.
But I have a problem with one sysctl, with other words, I can't find the
5.3 one for it.
sysctl: unknown oid 'kern.ps_argsopen'
Can someone help?
Thanks and kind regards,
Zeroke
[EMAIL PROTECTED
Hi all
I am running freebsd5.3 AMD and
I got error message from startup when Iadd the snmp
snmpd_enable=YES
snmpd_flags=-as -p /var/run/snmpd.pid
sysctl: physmem: Cannot allocate memory
What is the problem?
Thank you
__
Do you Yahoo
On Tue, 12 Oct 2004 01:33:44 -0400
epilogue [EMAIL PROTECTED] wrote:
On Mon, 11 Oct 2004 20:03:32 -0400
Chris Collins [EMAIL PROTECTED] wrote:
Hello Alll
I was wondering what is the best kern.securelevel to run on a
machine that provides general internet services, Web, FTP and Email.
Hello Alll
I was wondering what is the best kern.securelevel to run on a machine
that provides general internet services, Web, FTP and Email. I don't
want this so tight I cannot use the machine and I have also read in
some post that having the secure level set to high can stop a fsck.
I am
On Mon, 11 Oct 2004 20:03:32 -0400
Chris Collins [EMAIL PROTECTED] wrote:
Hello Alll
I was wondering what is the best kern.securelevel to run on a machine
that provides general internet services, Web, FTP and Email. I don't
want this so tight I cannot use the machine and I have also read in
Hi,
I wonder if there is a comprehensive list of what many of the sysctl
values are, both in terms of what the node (by this I mean, say,
hw.acpi.verbose) means, and what the values would mean/do?
If this doesn't exist would it be worth creating a website with a list
of all these? I've got
Lewis Thompson wrote:
I wonder if there is a comprehensive list of what many of the sysctl
values are, both in terms of what the node (by this I mean, say,
hw.acpi.verbose) means, and what the values would mean/do?
'sysctl -d -a hw' will give a one-line description for many of the sysctls
On Friday 17 September 2004 00:51, Lewis Thompson wrote:
Hi,
I wonder if there is a comprehensive list of what many of the sysctl
values are, both in terms of what the node (by this I mean, say,
hw.acpi.verbose) means, and what the values would mean/do?
I don't think there is. At the very
Before I install a new kernel and have to reboot a machine, I thought I'd
ask if there was a sysctl variable that can toggle the IPFIREWAL_FORWARD
option.
Tks.
Steve
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
- Original Message -
From: Steve Bertrand [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 09, 2004 4:22 PM
Subject: IPFIREWALL_FORWARD sysctl variable
| Before I install a new kernel and have to reboot a machine, I thought I'd
| ask if there was a sysctl variable that can
| Before I install a new kernel and have to reboot a machine, I thought
I'd
| ask if there was a sysctl variable that can toggle the IPFIREWAL_FORWARD
| option.
|
There's net.inet.ip.forwarding but i'm not sure if it's read only or even
perhaps if it exists/works without
Phil Schulz wrote:
Danny Howard wrote:
What's the easiest command to read to get good information on memory
usage? I played with /sbin/sysctl -n hw.physmem hw.usermem
vm.kvm_size vm.kvm_free yesterday but I have the feeling that these
are not the numbers I think they are, because they add up
Hi,
where can I find documentation on the vm.defer_swapspace_pageouts
sysctl? LINT only mentions it, without explaining, man sysctl doesn't
mention it at all, and even Google yields very few useful results...
I was looking for a way to tune swap-usage a bit, I heard Linux has a
swappiness
Geert Hendrickx wrote:
Hi,
where can I find documentation on the vm.defer_swapspace_pageouts
sysctl? LINT only mentions it, without explaining, man sysctl doesn't
mention it at all, and even Google yields very few useful results...
All I found in the source was this:
Give preference to dirty
I just tried setting the value of the kern.shutdown_timeout sysctl and it
failed with:
sysctl: unknown oid 'kern.shutdown_timeout'
I am trying to increase the maximum time allowed for rc.shutdown to run for
reasons explained in my previous post Help needed modifying shutdown
scripts
From
hi,
i found a strange case, i have tested the three machines(PIII 800
FreeBSD4.9-stable,
P4-1.6G FreeBSD4.8-release, P4-2.0G FreeBSD5.2.1).
I use sysctl -a | grep machdep.tsc.freq to get the CUP speed. But, I
failed on the P4-1.6G machine. Nothing appears.
Should I set some additional
ouyang kai wrote:
i found a strange case, i have tested the three machines(PIII 800
FreeBSD4.9-stable,
P4-1.6G FreeBSD4.8-release, P4-2.0G FreeBSD5.2.1).
I use sysctl -a | grep machdep.tsc.freq to get the CUP speed. But, I
failed on the P4-1.6G machine. Nothing appears.
Should I set some
Uwe wrote:
Is the P4-1.6G machine a multi-processor system, that is, was the kernel
compiled with the SMP option? If so, there is currently no TSC support
on multi-processor systems, for technical reasons I understand. So in
this case 'machdep.tsc.freq' is omitted from the kernel and
ouyang kai wrote:
Uwe wrote:
Is the P4-1.6G machine a multi-processor system, that is, was the kernel
compiled with the SMP option? If so, there is currently no TSC support
on multi-processor systems, for technical reasons I understand. So in
this case 'machdep.tsc.freq' is omitted from
On Mon, Nov 03, 2003 at 09:53:29PM -0500, Jud wrote:
On Mon, 3 Nov 2003 19:57:38 -0500, nw1 [EMAIL PROTECTED] wrote:
Basically, the machine is overheating (I believe)
because the cpu's aren't cycling down.
Previously I was able to cycle the processors down
with the following sysctl
parts of ipfw(8) and ipf(8) are code
inside of the kernel. The some of the behavior of ipfw(8) and ipf(8)
themselves are controlled by sysctl(8) knobs,
net.inet.ip.fw.enable
net.inet.ip.fw.one_pass
net.inet.ip.fw.debug
net.inet.ip.fw.verbose
...
net.inet.ipf.fr_flags
rules [ie: keep state] on all allow rules. I am
glad to meet you.
All the things below which I cut out of your how-to are MIB's in
sysctl, enabling them in the kernel source, or the setup rc.conf, or
in sysctl really makes no difference.
I have asked this question repeatedly over the months
On Tuesday 02 December 2003 18:29, fbsd_user wrote:
Thank you for responding with pointers to where I
can find some very limited documented info on the
MIB's I asked about.
You're welcome.
The only conclusion one can draw from the test results is that
IPFILTER gets access to the packets
Using
apropos sysctl
we get a list of several manpages, including blackhole(4), sysctl(3),
sysctl(8) and sysctl.conf(5).
These refer to several other sources, including ip(4), tcp(4), udp(4) and
rc.conf(5) - they also mention sys/sysctl.h, sys/socket.h,
netinet/in.h, netinet/icmp_var.h
be enabled (=1) on all systems
# man icmp(4) and inet(4) and man ip(4) do not contain info about
these MIB.
# man sysctl(3) does have info on ip.redirect
net.inet.icmp.drop_redirect=1
net.inet.icmp.log_redirect=0
net.inet.ip.redirect=0
# Source routing is another way for an attacker to try
The sysctl.conf file contains MIB's to change the default setting of
internal options of the kernel at boot up time.
I have found these MIB's when I display all the sysctl's.
These deal with how packets entering the FBSD system are handled by
default.
There are no man info on any MIB's.
I an
On Monday 01 December 2003 20:59, fbsd_user wrote:
net.inet.icmp.drop_redirect=1
net.inet.icmp.log_redirect=0
icmp(4)
net.inet.ip.redirect=0
net.inet.ip.sourceroute=0
net.inet.ip.accept_sourceroute=0
inet(4)
net.inet.icmp.bmcastecho=0
icmp(4)
net.inet.tcp.blackhole=2
-
From: Paul Mather [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 9:45 AM
Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable--
On Mon, 3 Nov 2003 21:07:45 -0700 (MST), Technical Director [EMAIL PROTECTED]
wrote:
= Forgive me
you have is defective by
design because it overheats under normal use and I wouldn't complain.
You can, of course, lobby the kernel maintainers to put those sysctl
variables back into FreeBSD, but chances are they took them out for a
good reason.
I'm not trying to mindlessly defend FreeBSD, either
Page updated-- http://69.3.136.141/freebsd/installation/sysctl_variables_missing One
(1)
question is still outstanding ... Yes=I'm still researching this.
-
All incoming attachments get deleted.
Have a nice day.
-
--sysctl variables
notavailable--
On Mon, 3 Nov 2003 19:57:38 -0500, nw1 [EMAIL PROTECTED] wrote:
What version of FreeBSD are you using?
Did you compile amp into the kernel?
I think you're not understanding what I posted @
http://69.3.136.141/freebsd/installation/sysctl_variables_missing
, Win2K is able to manage things so that the system
does not become so hot that the shutdown kicks in.
So, I'm wondering if there's some sysctl or other knob that can be set
in FreeBSD that will ameliorate this problem. (I thought
laptop/mobile CPUs generally were able to step down to lower
Jud, Annotated below
- Original Message -
From: Jud [EMAIL PROTECTED]
To: nw1 [EMAIL PROTECTED]; peter lageotakes [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 6:06 AM
Subject: Re: Overheating attributed to Freebsd --sysctl variables notavailable--
On Mon, 3
Paul mather,
Thanks for your response ...
See comments below (annotated)
- Original Message -
From: Paul Mather [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 9:45 AM
Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable--
On Mon, 3 Nov
annotated below
- Original Message -
From: Technical Director [EMAIL PROTECTED]
To: Paul Mather [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 12:32 PM
Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable--
= I doubt hardware
On Tue, 4 Nov 2003 14:05:02 -0500, nw1 [EMAIL PROTECTED] said:
[snip]
I'm interested in those missing sysctl variables I posted @
http://69.3.136.141/freebsd/installation/sysctl_variables_missing.
Using a Third party
application/script to fix something that was natively working
Jud, (see below)
- Original Message -
From: Jud [EMAIL PROTECTED]
To: nw1 [EMAIL PROTECTED]
Cc: freebsd-questions [EMAIL PROTECTED]
Sent: Tuesday, November 04, 2003 3:17 PM
Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable--
On Tue, 4 Nov 2003 14:05:02
On Tue, 4 Nov 2003 19:01:00 -0500, nw1 [EMAIL PROTECTED] wrote:
[snip]
Why mother board vendors release their products with such BIOS
settings?
What's the reason? nothing here
Not sure if this is what you were asking, but the reason is explained in
the quoted lines just below:
Well, there
The problem can be viewed @:
http://69.3.136.141/freebsd/installation/sysctl_variables_missing
Basically, the machine is overheating (I believe) because the cpu's aren't cycling
down.
Previously I was able to cycle the processors down with the following sysctl variables
/installation/sysctl_variables_missing implies; this was a
running system with no serious issues; meaning; the sysctl items I'm speaking of were
in
fact available and working.
If i can figure out how to make these sysctl variables available, I can set them like
they
were before, hence my overheating
with the following sysctl
variables:
machdep.apm_suspend_delay:
machdep.apm_standby_delay:
however, for some reason those variables currently, aren't any where to be found by
the
up_and_running system. Please use the hyperlink above for details.
Thanks for reading. All feedback is welcome.
Okay
PROTECTED]
To: nw1 [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, November 03, 2003 10:10 PM
Subject: Re: Overheating attributed to Freebsd --sysctl variables notavailable--
On Mon, 2003-11-03 at 17:38, nw1 wrote:
The problem can be viewed @:
http://69.3.136.141/freebsd/installation
running. The entire document @
http://69.3.136.141/freebsd/installation/sysctl_variables_missing
implies; this was a
running system with no serious issues; meaning; the sysctl items I'm
speaking of were in
fact available and working.
If i can figure out how to make these sysctl variables available
I'm interested in those missing sysctl variables I posted @
http://69.3.136.141/freebsd/installation/sysctl_variables_missing. Using a Third party
application/script to fix something that was natively working or under control, I don't
think, is the way to go and causes another level of complexity
.
Details @ http://69.3.136.141/freebsd/installation/sysctl_variables_missing
- Original Message -
From: jon [EMAIL PROTECTED]
To: nw1 [EMAIL PROTECTED]
Sent: Monday, November 03, 2003 10:00 PM
Subject: Re: Overheating attributed to Freebsd --sysctl variables notavailable--
On Mon, 2003-11-03
:00 PM
Subject: Re: Overheating attributed to Freebsd --sysctl variables notavailable--
On Mon, 2003-11-03 at 19:57, nw1 wrote:
What version of FreeBSD are you using?
Did you compile amp into the kernel?
I think you're not understanding what I posted @
http://69.3.136.141
Annotated below.
- Original Message -
From: Technical Director [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 03, 2003 11:07 PM
Subject: Re: Overheating attributed to Freebsd --sysctl variablesnotavailable--
Forgive me for saying:
No need to ask for forgiveness. I'm
; Where are those sysctl variables that i
was previously able to set? They are no longer available
You know, it's a good question - just for kicks, I tried this on my two
FreeBSD machines:
FreeBSD 4.9-RC #1: Wed Oct 15 08:12:11 PDT 2003:
# apm
apm: can't open /dev/apm: Device not configured
FreeBSD 4.8-RELEASE-p13
The machine overheats. sysctl variables unable to be seen.
Box-1 = NFS-server (the problem machine)
Box-2 and above are NFS-clients
The short version of the problem: After some overheating issues using:
Two (2) AMD 1800+ MP processors
In a Tyan Tiger MP (S-2460
After i started my
make buildworld
while it was building .. i noticed that the kernel sysctl was set to
sysctl -w kern.securelevel=2
i tried set it back to 0 or -1 ..but it wouldnt let me.
is it safe to reboot the system with the sysctl -w kern.securelevel
variable set to -1 ..AFTER the OS has
Hello,
Running 5.1-RELEASE, and was wondering is there a list of each sysctl
variable with a coresponding description? I know about sysctl -a and i pipe
that to a file, get something like 700 hits on it.
Thanks.
Dave.
___
[EMAIL PROTECTED
I would like to be able to set certain sysctl variables in the kernel,
preferably BEFORE the kernel finishes booting and runs init, etc. (or
at the worst case, very shortly after init runs) I thought I
remembered that there was a way to do this through the boot loader.
Can anyone enlighten
I would like to be able to set certain sysctl variables in the kernel,
preferably BEFORE the kernel finishes booting and runs init, etc. (or at
the worst case, very shortly after init runs) I thought I remembered
that there was a way to do this through the boot loader. Can anyone
enlighten
- Original Message -
From: Donald Burr [EMAIL PROTECTED]
To: FreeBSD Questions List [EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 6:11 PM
Subject: Setting sysctl variables BEFORE the kernel boots and runs init?
I would like to be able to set certain sysctl variables
Micheal Patterson wrote:
- Original Message -
From: Donald Burr [EMAIL PROTECTED]
To: FreeBSD Questions List [EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 6:11 PM
Subject: Setting sysctl variables BEFORE the kernel boots and runs init?
I would like to be able to set certain
On Thu, Aug 28, 2003 at 10:09:06AM +0200, David Landgren wrote:
Micheal Patterson wrote:
- Original Message -
From: Donald Burr [EMAIL PROTECTED]
To: FreeBSD Questions List [EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 6:11 PM
Subject: Setting sysctl variables BEFORE
Hiya folks -
Can someone tell me if there is a adverse effect in setting:
net.inet.ip.rtexpire from 3600 to say 5
And the same with net.inet.ip.rtminexpire fro 10 to say 2 ?
This would be on an ADSL wire.
Thanks in advance.
--
Best regards,
Chris
Chris [EMAIL PROTECTED] writes:
Can someone tell me if there is a adverse effect in setting:
net.inet.ip.rtexpire from 3600 to say 5
And the same with net.inet.ip.rtminexpire fro 10 to say 2 ?
This would be on an ADSL wire.
You don't want to drop it more than necessary, because
Hi.
Yesterday, 03.07.03 i did a cvsup and make world on my machine to
FreeBSD 5.1-CURRENT.
The strange thing is, when i type sysctl -a now, the system will
freeze. After a few second, it will automatically reboot. No logs for
that.
Is this a know problem?
asg
+-- Remington L. [freebsd] [30-06-03 21:17 -0700]:
| Is there a sysctl string that can tell me my uptime?
|
|
|
| --
you can get the uptime. indirectly.
sysctl kern.boottime
Regards,
Shantanu
--
You can look through a file
Is there a sysctl string that can tell me my uptime?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Mon, Jun 30, 2003 at 09:17:54PM -0700 or thereabouts, Remington L. wrote:
Is there a sysctl string that can tell me my uptime?
No, but kern.boottime is the boot time of the kernel, so subtract that from
`date +%s` and you have uptime in seconds. Note that sysctl's output for this
field
Hi. I'm seeking suggestions for sysctl variables to use on a highly-taxed
mission-critical file-server. This computer exports two 630GB arrays via
SAMBA over gigabit on 3ware escalades. Anyone have any tips?
The reason I'm asking is because smbd has been dropping processes lately. I
recently
[snip]
6 Nov 21 04:20:01 fnord /kernel: Limiting icmp unreach response from 208 to
200 packets per second
This is because you have 'options ICMP_BANDLIM' in your kernel config.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
net.inet.icmp.icmplim: 200
using sysctl.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Hi.
6 Nov 21 04:20:01 fnord /kernel: Limiting icmp unreach response from
208
to 200 packets per second
This is because you have 'options ICMP_BANDLIM' in your kernel config.
Further more you can increase this by setting net.inet.icmp.icmplim: 200
using sysctl.
That's what I
In the last episode (Nov 21), David Smithson said:
Hi. I'm seeking suggestions for sysctl variables to use on a
highly-taxed mission-critical file-server. This computer exports two
630GB arrays via SAMBA over gigabit on 3ware escalades. Anyone have
any tips?
The reason I'm asking
Hi list
How can i write a variable that can be accessed by the sysctl command like
the other kernel variable ( i want to have int and char * for ip layer
files)
thanx
_
Join the worlds largest e-mail service with MSN Hotmail
Hi,
I am currently trying to get a route dump in
freebsd4.4 using sysctl with NET_RT_DUMP.
I am running into problems while parsing the returned
rt_msghdr structures.
The sockaddr structures returned after the rt_msghdr
are messed up and it is not giving correct gateway or
netmask.
For ex
101 - 191 of 191 matches
Mail list logo
