Bug 761849 (GLUSTER-117) - Wrong command line does not throw error
Summary: Wrong command line does not throw error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-117
Product: GlusterFS
Classification: Community
Component: unclassified
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Basavanagowda Kanur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-08 08:54 UTC by Sachidananda Urs
Modified: 2009-11-26 06:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTA
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sachidananda Urs 2009-07-08 05:59:33 UTC 
This does not log in /var/log/glusterfs/* either...
Comment 1 Sachidananda Urs 2009-07-08 06:13:00 UTC 
Log messages are logged in defaultdir/var/log...

When glusterfs is not started, the return value should not be 0.
Comment 2 Sachidananda Urs 2009-07-08 08:54:29 UTC 
When I start glusterfs without a -l option for eg:

/opt/glusterfs/2.0.3/sbin/glusterfs -f /share/sac/volfiles/2.0.3/distribute/client.vol /share/sac/log/2.0.3/distribute/client.2.0.3.distribute.client02.log --run-id distributetest

The command executes with a return value of 0.
And glusterfs is not started.

Where as this should throw a error, and return a non-zero return status.
Comment 3 Anand Avati 2009-10-05 09:16:50 UTC 
PATCH: http://patches.gluster.com/patch/1665 in master (glusterfsd.c: Pipe is used during daemonization as ipc.)
Comment 4 Anand Avati 2009-10-05 09:17:08 UTC 
PATCH: http://patches.gluster.com/patch/1669 in release-2.0 (glusterfsd.c:Pipe is used during daemonization as ipc.)
Note You need to log in before you can comment on or make changes to this bug.