Bug 501200 - incorrect exit codes - invalid interface and invalid capture filter
incorrect exit codes - invalid interface and invalid capture filter
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: wireshark (Show other bugs)
5.3
All Linux
low Severity low
: rc
: ---
Assigned To: Radek Vokal
BaseOS QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-17 18:20 EDT by Katerina Novotna
Modified: 2009-05-18 16:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-05-18 02:44:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Katerina Novotna 2009-05-17 18:20:43 EDT
Description of problem:
Tethereal returned incorrect exit codes in this cases:
- input is invalid name of interface
- input is invalid capture filter

Version-Release number of selected component (if applicable):
1.0.3

How reproducible:
always

Steps to Reproduce:
RHTS test
/usr/bin/single_package.py -S rhts.redhat.com  -e development  -u username@redhat.com  -a i386   -d RHEL5-Client-U3  -t /CoreOS/wireshark/Crasher/tethereal/exit-codes

  
Actual results:
exit code is 0

Expected results:
exit code 1

Additional info:
I am using tethereal in subsequent command line pipeline and the current behavior is misleading, so I can't detect tethereal failures due it.
Comment 1 Radek Vokal 2009-05-18 02:44:10 EDT
Please, retest with the latest wireshark version.
Comment 2 Katerina Novotna 2009-05-18 16:38:15 EDT
version 1.0.7, development version 1.1.3 and current cvs version has the same result.

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