This wiki is obsolete, see the NorduGrid web pages for up to date information.
Testing/test arched command line EMI1 RC3
F2: arched command line options
- Tester: Jon
- due: 25 March
Started with a clean SL5.5 x86_64 virtual machine, installed from EMI1 RC2 following ARC client installation instructions (http://www.nordugrid.org/documents/arc-client-install.html).
yum install nordugrid-arc-hed yum install nordugrid-arc-plugins-globus
Test the command line options of arched, if they work according to documentation.
- -d, --config-dump dump generated XML config
- check if ini config is correctly translated using different ini config files
- -h, --help Show help options
- -f, --foreground run daemon in foreground
- -c, --xml-config=path full path of XML config file
- -i, --ini-config=path full path of InI config file
- -p, --pid-file=path full path of pid file
- -u, --user=user user name
- -g, --group=group group name
- -s, --schema=path full path of XML schema file
- -v, --version print version information
F2.1: Dump generated XML config
Description of the test:
Create ini-files for all services available in /usr/share/arc/profiles/general.xml. Check if correct XML config is dumped.
Testbed:
arched deployed on resource described.
Expected result:
Dumped XML config can be used to start corresponding service.
Result:
F2.2: Show help options
Description of the test:
Run arched with help option.
Testbed:
arched deployed on resource described.
Expected result:
Help options are showed both with short and long option. Help options correspond to man page.
Result: PASSED
F2.3: Run daemon in foreground
Description of the test:
Run arched with foreground option.
Testbed:
arched deployed on resource described.
Expected result:
arched is run in the foreground both with long and short option.
Result: PASSED
F2.4: full path of XML config file
Description of the test:
Run arched with XML config file option. Give XML file as input.
Testbed:
arched deployed on resource described.
Expected result:
arched starts what is described in the given XML file and not in the default XML file.
Result: PASSED
F2.5: full path of Ini config file
Description of the test:
Run arched with Ini config file option. Give Ini file as input.
Testbed:
arched deployed on resource described.
Expected result:
arched starts what is described in the given Ini file and not the default Ini file.
Result: PASSED
F2.6: full path of of pid file
Description of the test:
Run arched with pid file option.
Testbed:
arched deployed on resource described.
Expected result:
Starting arched creates pid file on given path.
Result: PASSED
F2.7: user name
Description of the test:
Run arched with user name option.
Testbed:
arched deployed on resource described.
Expected result:
arched process is owned by given user.
Result: PASSED
F2.8: group name
Description of the test:
Run arched with group name option.
Testbed:
arched deployed on resource described.
Expected result:
arched process is owned by given group.
Result:PASSED
F2.9: full path of XML schema file
Description of the test:
Run arched with XML schema option on echo XML config.
Testbed:
arched deployed on resource described.
Expected result:
Given schema file is used and and XML config is validated .
Result: Failed Output was:
# arched -c echo.xml -s /usr/share/arc/schema/echo.xsd element ArcConfig: Schemas validity error : Element '{http://www.nordugrid.org/schemas/loader/2009/08}ArcConfig': No matching global declaration available for the validation root. [2011-04-04 14:31:59] [Arc] [ERROR] [5263/135994816] Schema validation error [2011-04-04 14:31:59] [Arc] [ERROR] [5263/135994816] (empty)"
[#2361]
F2.10: version
Description of the test:
Run arched with version option.
Testbed:
arched deployed on resource described.
Expected result:
Version 1.0.0b4 is printed and arched is not running.
Result: PASSED