Bug 475963

Summary: slabtop -o is broken?
Product: Red Hat Enterprise Linux 5 Reporter: Petr Šplíchal <psplicha>
Component: procpsAssignee: Daniel Novotny <dnovotny>
Status: CLOSED ERRATA QA Contact: BaseOS QE <qe-baseos-auto>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.3CC: albert, ohudlick, ovasik, rvokal, tao
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 08:06:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch for slabtop -o none

Description Petr Šplíchal 2008-12-11 11:01:36 UTC 
Using slabtop with --once option erases curses window just after
displaying the contents, so in this way it's quite useles. There
should be no erase and the data should be displayed in stdout.

Issue present in procps-3.2.7-11.1.el5

+++ This bug was initially created as a clone of Bug #437476 +++

According to the slabtop(8) manual page:

	--once, -o
              Display the output once and then exit.

However, this is not the case:

# slabtop -o
# echo $?
0

Please fix.

Thanks,
Peter

--- Additional comment from dnovotny on 2008-09-24 06:08:57 EDT ---

hello,

I analyzed the problem, it is indeed a bug, and I found a solution:

the problem was, that the output went to curses and disappeared after
endwin(), so I managed to print it, when "-o" option is used, to stdout
instead
Comment 1 Daniel Novotny 2008-12-11 12:38:40 UTC 
Created attachment 326609 [details]
patch for slabtop -o

okay, patch ported to RHEL5 version of procps
Comment 4 Daniel Novotny 2009-11-19 14:39:47 UTC 
fixed in procps-3.2.7-12.el5
Comment 8 errata-xmlrpc 2010-03-30 08:06:32 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0200.html