From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] syscall spikes
Date: Tue, 17 Apr 2007 11:45:29 -0400 [thread overview]
Message-ID: <61909b30c2fd4aed1dc3174595a1e4a7@coraid.com> (raw)
In-Reply-To: <9ab217670704170838g363bba09pc0328e13106d0efd@mail.gmail.com>
are you running anything that faces the outside world that
might be doing auth? if you don't have a /sys/log/auth, you
might want to create it and watch it for any external attacks.
i've found that to be a source of big syscall loads on some of
our systems.
- erik
On Tue Apr 17 11:38:33 EDT 2007, devon.odell@gmail.com wrote:
> 2007/4/17, Devon H. O'Dell <devon.odell@gmail.com>:
> > 2007/4/17, Uriel <uriel99@gmail.com>:
> > > fossil
> >
> > I attempted to tprof fossil and I don't get any useful output. I even did:
> >
> > for (i in `{ps a | grep fossil | awk '{ print $2 }'})
> > echo profile > /proc/$i/ctl
> >
> > [wait a while for spike]
> >
> > for (i in `{ps a | grep fossil | awk '{ print $2 }'}) {
> > echo $i
> > tprof $i
> > }
> >
> > All I get is a bunch of lines saying ``total: 0''.
> >
> > What'm I missing? :(
>
> I found the [undocumented] startsyscall argument to the process ctl
> file, but I cannot get it to work. If I echo startsyscall >
> /proc/N/ctl, I get ``echo: write error: bad process or channel control
> request''.
>
> What gives?
>
> --dho
>
> > --dho
> >
> > > On 4/17/07, Devon H. O'Dell <devon.odell@gmail.com> wrote:
> > > > Hi,
> > > >
> > > > I've been having syscall spikes. It's really weird. There will be
> > > > >40,000 in 1 second, (according to stats(8)) and it appears at a
next prev parent reply other threads:[~2007-04-17 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 14:15 Devon H. O'Dell
2007-04-17 14:36 ` Uriel
2007-04-17 15:22 ` Devon H. O'Dell
2007-04-17 15:38 ` Devon H. O'Dell
2007-04-17 15:45 ` erik quanstrom [this message]
2007-04-17 15:56 ` Devon H. O'Dell
2007-04-17 16:29 ` Devon H. O'Dell
2007-04-17 16:39 ` Devon H. O'Dell
2007-04-17 15:49 ` Charles Forsyth
2007-04-18 16:53 ` Russ Cox
2007-04-18 16:59 ` Devon H. O'Dell
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=61909b30c2fd4aed1dc3174595a1e4a7@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).