Bug 139463 - Spinning on rhgb-console
Summary: Spinning on rhgb-console
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rhgb   
(Show other bugs)
Version: 3
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-16 03:43 UTC by Owen Taylor
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-29 13:15:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Owen Taylor 2004-11-16 03:43:57 UTC
http://www.redhat.com/archives/fedora-devel-list/2004-November/msg00561.html

reveals that rhgb spins at 100% cpu during boot. Some inspection
of the source code reveals this is do to the handling of
rhgb-console... it calls poll() on a fifo ... and fifo's have
the behavior that once the last writer closes the fifo, it 
reports HUP until a new reader opens it.

Googling on the topic reveals:

http://mail.gnome.org/archives/gtk-list/2002-September/msg00275.html

with an IRC snippet from myself about the topic. 

Two possible workarounds are suggested there:

 - Close the fifo and reopen it ...doesn't work here since
   we might lose data

 - open the fifo read/write so there are never 0 writers.

Basically, my conclusion has always been that fifo's are just
evil, poorly defined creatures. I think the O_RDWR hack will
work, at least on linux. I'm not sure it wouldn't be long
term to replace '> /etc/rhgb/temp/rhgb-console' with
'| rhgb-client --echo' or something.

Comment 1 Daniel Veillard 2004-11-16 09:10:32 UTC
I see, ouch ... I will try to fix ASAP.

Daniel

Comment 2 Brian Long 2004-11-29 12:54:49 UTC
I assume this also affects RHEL 3 U2 and beyond since rhgb is now
included.  Is that correct?  Will an update to rhgb be available
before U5?

Comment 3 Daniel Veillard 2004-11-29 13:14:10 UTC
RHEL 3 U2 seems to use rhgb-0.11.2 which is not affected by that bug.
Updating to the latest doesn't sound resonnable it would require to
upgrade a number of other pieces.

Daniel

Comment 4 Daniel Veillard 2004-11-29 13:15:40 UTC
The original bug has been fixed with a FC3 update rhgb-0.15.1

Daniel


Note You need to log in before you can comment on or make changes to this bug.