On Fri, Dec 19, 2008 at 01:04:26PM -0500, FreeBSD wrote:
> Tom Worster a écrit :
> >On 12/19/08 10:37 AM, "FreeBSD" wrote:
> >
> >
> >>Because this server is monitored by Nagios and it emails me every hour a
> >>warning because the swap is not 100% free (I know it's pretty extreme,
> >>but I wa
On Fri, Dec 19, 2008 at 10:37:46AM -0500, FreeBSD wrote:
> Jerry McAllister a écrit :
> >On Thu, Dec 18, 2008 at 12:02:06PM -0500, FreeBSD wrote:
> >
> >
> >>Daniel Bye a écrit :
> >>
> >>>On Thu, Dec 18, 2008 at 10:28:18AM -0600, Kirk Strauser wrote:
> >>>
> On Thursday 18 Decembe
On Friday 19 December 2008 19:04:26 FreeBSD wrote:
> This server is very lightly used, so most of the time if the swap is
> getting used it shows that something is going wrong. This warning
> already proved usefull once, so I don't think I'm going to change it.
Swapping is a symptom of a symptom
On Dec 19, 2008, at 12:04 PM, FreeBSD wrote:
This server is very lightly used, so most of the time if the swap is
getting used it shows that something is going wrong.
No it doesn't. Get that wrong idea out of your head.
--
Kirk Strauser
___
f
On Fri, 19 Dec 2008 13:04:26 -0500
FreeBSD wrote:
> This server is very lightly used, so most of the time if the swap is
> getting used it shows that something is going wrong. This warning
> already proved usefull once, so I don't think I'm going to change it.
> I don't want to mess with the
Tom Worster a écrit :
On 12/19/08 10:37 AM, "FreeBSD" wrote:
Because this server is monitored by Nagios and it emails me every hour a
warning because the swap is not 100% free (I know it's pretty extreme,
but I want to know if the system is swapping).
if a swap space is available and
On 12/19/08 10:37 AM, "FreeBSD" wrote:
> Because this server is monitored by Nagios and it emails me every hour a
> warning because the swap is not 100% free (I know it's pretty extreme,
> but I want to know if the system is swapping).
if a swap space is available and swapping not turned off, it
but it's still played around with 3MB of swap. This is not hurting anything,
and absolutely is *not* an indication that anything is wrong or sub-optimal.
Seriously, get over your obsession with keeping swap utterly empty before it
drives you nuts. FreeBSD isn't designed to work that way and y
jerry
Because this server is monitored by Nagios and it emails me every hour a
warning because the swap is not 100% free (I know it's pretty extreme, but I
want to know if the system is swapping).
I just tried
swapoff -a ; swapon -a
and it worked great.
under completely normal operati
On Dec 19, 2008, at 9:37 AM, FreeBSD wrote:
Because this server is monitored by Nagios and it emails me every
hour a warning because the swap is not 100% free (I know it's pretty
extreme, but I want to know if the system is swapping).
Martin,
I'm not trying to be harsh, honestly, but stop
Jerry McAllister a écrit :
On Thu, Dec 18, 2008 at 12:02:06PM -0500, FreeBSD wrote:
Daniel Bye a écrit :
On Thu, Dec 18, 2008 at 10:28:18AM -0600, Kirk Strauser wrote:
On Thursday 18 December 2008 09:16:10 FreeBSD wrote:
Hi everyone,
I have a FreeBSD 7.0-Release serv
RW a écrit :
On Thu, 18 Dec 2008 15:13:12 -0500
FreeBSD wrote:
I can't see any process within parentheses in top... I also looked at
the -f option of ps but the process that caused the swapping are not
listed.
FreeBSD only swaps in extreme cases - most of the time it's paging
inst
To others: There is one reason I can think of for doing this, if an
irregularly used program (that is rather big) has been swapped out but
requires a low latency when used (i.e. must not wait to be swapped back
so change this program if it requires low latency to do mlockall
_
On Thursday 18 December 2008 17:16:10 FreeBSD wrote:
> Hi everyone,
>
> I have a FreeBSD 7.0-Release server that started to swap after an error
> in a shell script (process spawning competition ;-) ). I killed the
> shell and the RAM is now OK. The problem is that the swap is still used.
> How can
On Thu, Dec 18, 2008 at 12:02:06PM -0500, FreeBSD wrote:
> Daniel Bye a écrit :
> >On Thu, Dec 18, 2008 at 10:28:18AM -0600, Kirk Strauser wrote:
> >>On Thursday 18 December 2008 09:16:10 FreeBSD wrote:
> >>>Hi everyone,
> >>>
> >>>I have a FreeBSD 7.0-Release server that started to swap after an
On Thu, 18 Dec 2008 15:13:12 -0500
FreeBSD wrote:
> I can't see any process within parentheses in top... I also looked at
> the -f option of ps but the process that caused the swapping are not
> listed.
>
FreeBSD only swaps in extreme cases - most of the time it's paging
instead.
If it really
On Thursday 18 December 2008 14:13:12 FreeBSD wrote:
> I can't see any process within parentheses in top... I also looked at
> the -f option of ps but the process that caused the swapping are not
> listed.
Dude. For real. Quit sweating it. Let the system do what it needs to do;
chances are it
Daniel Bye a écrit :
On Thu, Dec 18, 2008 at 12:02:06PM -0500, FreeBSD wrote:
Daniel Bye a ?crit :
On Thu, Dec 18, 2008 at 10:28:18AM -0600, Kirk Strauser wrote:
On Thursday 18 December 2008 09:16:10 FreeBSD wrote:
Hi everyone,
I have a FreeBSD 7.0-Release server that started to swap after a
On Thursday 18 December 2008 11:02:06 FreeBSD wrote:
> Thanks for your answer. I'm asking here because it's been several days
> and there is still used swap for data that should never be used anymore.
> If the kernel wants to keep it, why not move it to RAM now that there is
> some free?
Do you *
On Thu, Dec 18, 2008 at 12:02:06PM -0500, FreeBSD wrote:
> Daniel Bye a ?crit :
> >On Thu, Dec 18, 2008 at 10:28:18AM -0600, Kirk Strauser wrote:
> >>On Thursday 18 December 2008 09:16:10 FreeBSD wrote:
> >>>Hi everyone,
> >>>
> >>>I have a FreeBSD 7.0-Release server that started to swap after an e
Daniel Bye a écrit :
On Thu, Dec 18, 2008 at 10:28:18AM -0600, Kirk Strauser wrote:
On Thursday 18 December 2008 09:16:10 FreeBSD wrote:
Hi everyone,
I have a FreeBSD 7.0-Release server that started to swap after an error
in a shell script (process spawning competition ;-) ). I killed the
shel
I have a FreeBSD 7.0-Release server that started to swap after an error in a
shell script (process spawning competition ;-) ). I killed the shell and the
RAM is now OK. The problem is that the swap is still used. How can I "reset"
the swap?
you don't need. something got swapped out, and will b
On Thu, Dec 18, 2008 at 10:28:18AM -0600, Kirk Strauser wrote:
> On Thursday 18 December 2008 09:16:10 FreeBSD wrote:
> > Hi everyone,
> >
> > I have a FreeBSD 7.0-Release server that started to swap after an error
> > in a shell script (process spawning competition ;-) ). I killed the
> > shell an
On Thursday 18 December 2008 09:16:10 FreeBSD wrote:
> Hi everyone,
>
> I have a FreeBSD 7.0-Release server that started to swap after an error
> in a shell script (process spawning competition ;-) ). I killed the
> shell and the RAM is now OK. The problem is that the swap is still used.
> How can
Hi everyone,
I have a FreeBSD 7.0-Release server that started to swap after an error
in a shell script (process spawning competition ;-) ). I killed the
shell and the RAM is now OK. The problem is that the swap is still used.
How can I "reset" the swap?
Thanks for sharing your knowledge,
Ma
25 matches
Mail list logo
