Bug 471637 - bad error message if --module-dir is not a directory.
Summary: bad error message if --module-dir is not a directory.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: beta
Hardware: All
OS: Linux
medium
low
Target Milestone: 1.1
: ---
Assignee: Gordon Sim
QA Contact: Kim van der Riet
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-14 19:07 UTC by Alan Conway
Modified: 2009-03-20 08:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-20 08:10:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alan Conway 2008-11-14 19:07:55 UTC 
Description of problem:

Start qpidd with a filename for --module-dir, gives a meaningless error message:

qpidd --module-dir .libs/cluster.so --help
boost::filesystem::basic_directory_iterator constructor

Expected results:

Meangingful message e.g.

Invalid value for module-dir: ".libs/cluster.so" is not a directory.

Additional info:
Comment 1 Gordon Sim 2008-11-24 12:42:18 UTC 
Fixed by r720177.
Comment 2 Frantisek Reznicek 2008-11-28 07:44:42 UTC 
The issue has been fixed.
Validated on RHEL 4.7 / 5.2 i386 / x86_64 on latest packages (qpidd-0.3.719671-1.el5) and latest sources (rev: 721356), with following results:

[freznice@dhcp-lab-200 src]$ ./qpidd --module-dir .libsf/cluster.so --help
2008-nov-28 08:43:50 critical Broker start-up failed: Directory not found: .libsf/cluster.so
[freznice@dhcp-lab-200 src]$ echo $?
1

[freznice@dhcp-lab-200 direct]$ /usr/sbin/qpidd --module-dir .libsf/cluster.so --help
2008-nov-28 08:44:15 critical Broker start-up failed: Directory not found: .libsf/cluster.so
[freznice@dhcp-lab-200 direct]$ echo $?
1


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