Bug 679833

Summary:	[RFE] tailf should support `-n 0`
Product:	Red Hat Enterprise Linux 6	Reporter:	Michal Nowak <mnowak>
Component:	util-linux-ng	Assignee:	Karel Zak <kzak>
Status:	CLOSED ERRATA	QA Contact:	Branislav Blaškovič <bblaskov>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.1	CC:	azelinka, bblaskov, ohudlick, ovasik, rvokal
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	util-linux-ng-2.17.2-12.8.el6	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 10:22:25 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:
Bug Depends On:
Bug Blocks:	836160, 840699

Description Michal Nowak 2011-02-23 16:28:12 UTC

Description of problem:

tail supports `-n 0` in it's `-f` "mode":

  tail -f -n 0 file

so should tailf:

[newman@dhcp-25-28 tmp]$ tailf -n 0 file 
tailf: invalid number of lines

Thus I propose tailf to be able to print out zero-length output from watched log file.

(Sorry to put it here, I failed to find upstream Bugzilla and didn't want to write o m-l w/o patch.)

Comment 2 Karel Zak 2011-03-18 08:54:30 UTC

Fixed by upstream commit 127b12dcf6bd1a150fa2ebdec3161fcddab9ada6. It should be possible to backport the patch to RHEL6.

Comment 4 Suzanne Logcher 2012-01-31 21:17:14 UTC

This request was evaluated by Red Hat Product Management for inclusion in the
current release of Red Hat Enterprise Linux. Because the affected component is
not scheduled to be updated in the current release, Red Hat is unfortunately
unable to address this request at this time.  It has been proposed for the next
release. If you would like it considered as an exception in the current
release, please ask your support representative.

Comment 11 errata-xmlrpc 2013-02-21 10:22:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0517.html