public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Carey M. Drake" <carey.drake@oracle.com>
To: Byron Stanoszek <gandalf@winds.org>
Cc: "J.D. Hollis" <jdhollis@cc.gatech.edu>, linux-kernel@vger.kernel.org
Subject: Re: major problem with linux-2.4.0test10
Date: Wed, 08 Nov 2000 15:53:02 -0500	[thread overview]
Message-ID: <3A09BD2E.46E07FFA@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011081533320.13062-100000@winds.org>

Why not just remove the sa lines from /etc/crontab?

C.

Byron Stanoszek wrote:
> 
> On Wed, 8 Nov 2000, J.D. Hollis wrote:
> 
> > I've been having a problem with memory since 2.4.0test9...for some reason,
> > shortly after my system boots, my hard drive begins to seek rapidly for no
> > apparent reason, and suddenly about 150MB of my 256MB RAM is filled up with
> > something gtop labels 'Other.'  whatever's filling my memory isn't attached
> > to any process.   the one time I managed to get gtop open while the hard
> > drive was seeking, I noticed that kflushd was using about 98% of my
> > processor (an Athlon 900MHz).  I'm running Redhat 7.0 (although I have no
> > idea whether that makes a difference).
> 
> It's probably a program called 'sa' that anacron starts up right after boot
> (on RH 7.0). It's a system accounting program that starts up and scans the
> entire drive looking for stuff, which fills up cache in RAM.
> 
> I generally disable all anacron stuff and remove /etc/cron.??* and the
> daily/weekly/monthly entries in /etc/crontab, then I run
> '/etc/rc.d/init.d/crond restart'. That oughta fix it, but you might want to
> look into the cron scripts individually and selectively remove the lines you
> don't want. :-)
> 
> --
> Byron Stanoszek                         Ph: (330) 644-3059
> Systems Programmer                      Fax: (330) 644-8110
> Commercial Timesharing Inc.             Email: bstanoszek@comtime.com
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

-- 
C.

------------------------------------------------------------------------------  

When in doubt, poke it with a stick

Disclaimer: the above is the author's personal opinion and is not the
opinion
or policy of his employer or of the little green men that have been
following
him all day.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-08 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-08 17:54 major problem with linux-2.4.0test10 J.D. Hollis
2000-11-08 20:36 ` Byron Stanoszek
2000-11-08 20:53   ` Carey M. Drake [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A09BD2E.46E07FFA@oracle.com \
    --to=carey.drake@oracle.com \
    --cc=gandalf@winds.org \
    --cc=jdhollis@cc.gatech.edu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox