supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Count László de Almásy" <calmasy@gmail.com>
To: "Charlie Brady" <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: OpenSim.exe causes cpu spike (Re: supervise causes cpu spike)
Date: Sun, 14 Dec 2008 07:26:58 +0500	[thread overview]
Message-ID: <abb783b90812131826k355e4f83vf981b63d42f2159a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812131843090.10503@e-smith.charlieb.ott.istop.com>

On Sun, Dec 14, 2008 at 4:49 AM, Charlie Brady
<charlieb-supervision@budge.apana.org.au> wrote:
> Try:
>
> exec setuidgid opensim mono OpenSim.exe </dev/null
>
> or
>
> exec </dev/null
> exec setuidgid opensim mono OpenSim.exe

I tried both to no avail. Behavior is the same. Any other suggestions?

> No, it's that the process is repeatedly reading standard input in
> non-blocking mode, without first checking that there are any bytes to read.
>
> That's a bug in OpenSim.exe (or in mono).
>
> If it is a supervised daemon process, why is it reading standard input?

I'll see about reporting this to the OpenSim dev team.

-- 
Cheers, László


  reply	other threads:[~2008-12-14  2:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 22:33 supervise causes cpu spike Count László de Almásy
2008-12-13 23:49 ` OpenSim.exe causes cpu spike (Re: supervise causes cpu spike) Charlie Brady
2008-12-14  2:26   ` Count László de Almásy [this message]
2008-12-14  6:04     ` Charlie Brady
2008-12-14  6:18       ` Count László de Almásy
2008-12-16 10:48 ` supervise causes cpu spike Laurent Bercot

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=abb783b90812131826k355e4f83vf981b63d42f2159a@mail.gmail.com \
    --to=calmasy@gmail.com \
    --cc=charlieb-supervision@budge.apana.org.au \
    --cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).