[9174] in athena10
Re: [Debathena] #775: Cluster logouts are slow because of schroot
daemon@ATHENA.MIT.EDU (Debathena Trac)
Sun Jun 3 14:05:02 2012
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: broder@MIT.EDU, jdreed@MIT.EDU, andersk@MIT.EDU
Date: Sun, 03 Jun 2012 18:04:58 -0000
Reply-To:
Message-ID: <057.d4a576949c853dd045366e8ede8ac502@mit.edu>
In-Reply-To: <042.0a609fd164ac0982b95ebc0ed4a9dbd8@mit.edu>
Content-Transfer-Encoding: 8bit
#775: Cluster logouts are slow because of schroot stupidity
--------------------------+-----------------------------
Reporter: broder | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Precise Beta
Component: login chroot | Resolution:
Keywords: | Upstream bug:
--------------------------+-----------------------------
Comment (by jdreed):
FWIW, here are the processes that don't immediately shut down 1 second
after a TERM:
- zwgc (2 secs)
- dbus-launch (3 secs)
pulseaudio almost never shuts down cleanly and requires a kill.
Even after a SIGKILL, pulseaudio and dbus-daemon can take up to 2 seconds
to actually die, and I'm fairly certain that's what's triggering our
reboot code more often than we expect. The new reactivate logging agrees
with me.
Refactoring the loops takes our logout time down to 7 seconds, which is
noticeably better. We should still try and figure out why pulseaudio is
sticking around, though.
--
Ticket URL: <https://athena10.mit.edu/trac/ticket/775#comment:5>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
