[FALCON-162] Update falcon scripts to let the user set the log and pid locations.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3
• Fix Version/s: 0.4
• Assignee: Arpit Gupta
• Reporter: Arpit Gupta
• Created: 30/Oct/13 23:12
• Updated: 12/Nov/13 06:11
• Resolved: 12/Nov/13 06:11

Description

Current falcon scripts hard code the location of the log and the pid dirs. Instead if we added the ability to source a falcon-env.sh which the user could provide then the user can overwrite these locations to some thing else.

This would also allow the user a way to set JAVA_HOME and other env vars in a file rather than doing it in a shell. This is something similar to how hadoop works.

Along with this change i also plan on changing the classpath to list dir/* instead of every jar file. Again this is similar to what hadoop 2 does.

Issue Links

• is duplicated by: FALCON-148 Falcon start script problem
• is required by: FALCON-187 Update Falcon start script to also redirect stdout to the log file
• is required by: FALCON-165 simplify packaging to create one package instead of client, falcon and prism packages