Bug 761849 (GLUSTER-117)

Summary: Wrong command line does not throw error
Product: [Community] GlusterFS Reporter: Sachidananda Urs <sac>
Component: unclassifiedAssignee: Basavanagowda Kanur <gowda>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs, vinayak
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTA Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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.)