{ "info": { "author": "Michael Meffie", "author_email": "mmeffie@sinenomine.net", "bugtrack_url": null, "classifiers": [ "Development Status :: 4 - Beta", "Environment :: Console", "Intended Audience :: Developers", "License :: OSI Approved :: MIT License", "Operating System :: POSIX :: Linux", "Operating System :: POSIX :: SunOS/Solaris", "Programming Language :: Python :: 2", "Programming Language :: Python :: 2.6", "Programming Language :: Python :: 2.7", "Topic :: Utilities" ], "description": "=======\nafsutil\n=======\n\n**afsutil** is a command-line tool to build, install, and setup OpenAFS for\ndevelopers and testers.\n\nCommand line interface\n----------------------\n\n::\n\n usage: afsutil [options]\n\n commands:\n version Print version\n help Print usage\n getdeps Install build dependencies\n check Check hostname\n build Build binaries\n reload Reload the kernel module from the build tree\n package Build packages\n install Install binaries\n remove Remove binaries\n start Start AFS services\n stop Stop AFS services\n ktcreate Create a fake keytab\n ktdestroy Destroy a keytab\n ktsetkey Add a service key from a keytab file\n ktlogin Obtain a token with a keytab\n newcell Setup a new cell\n mtroot Mount root volumes in a new cell\n addfs Add a new fileserver to a cell\n\nExamples\n--------\n\nTo build OpenAFS from sources::\n\n $ git clone git://git.openafs.org/openafs.git\n $ cd openafs\n $ afsutil build\n\nTo install legacy \"Transarc-style\" binaries::\n\n $ sudo afsutil install \\\n --force \\\n --components server client \\\n --dist transarc \\\n --dir /usr/local/src/openafs-test/amd64_linux26/dest \\\n --cell example.com \\\n --realm EXAMPLE.COM \\\n --hosts myhost1 myhost2 myhost3 \\\n --csdb /root/CellServDB.dist \\\n -o \"afsd=-dynroot -fakestat -afsdb\" \\\n -o \"bosserver=-pidfiles\"\n\nTo setup the OpenAFS service key from a Kerberos 5 keytab file::\n\n $ sudo afsutil setkey\n --cell example.com \\\n --realm EXAMPLE.COM \\\n --keytab /root/fake.keytab\n\nTo start the OpenAFS servers::\n\n $ sudo afsutil start server\n\nTo setup a new OpenAFS cell on 3 servers, after 'afsutil install' has been run\non each::\n\n $ sudo afsutil newcell \\\n --cell example.com \\\n --realm EXAMPLE.COM \\\n --admin example.admin \\\n --top test \\\n --akimpersonate \\\n --keytab /root/fake.keytab \\\n --fs myhost1 myhost2 myhost3 \\\n --db myhost1 myhost2 myhost3 \\\n --aklog /usr/local/bin/aklog-1.6 \\\n -o \"dafs=yes\" \\\n -o \"afsd=-dynroot -fakestat -afsdb\" \\\n -o \"bosserver=-pidfiles\" \\\n -o \"dafileserver=L\"\n\nTo start the client::\n\n $ sudo afsutil start client\n\nTo mount the top-level volumes after the client is running::\n\n $ afsutil mtroot \\\n --cell example.com \\\n --admin example.admin \\\n --top test \\\n --realm EXAMPLE.COM \\\n --akimpersonate \\\n --keytab /root/fake.keytab \\\n --fs myhost1 \\\n -o \"afsd=-dynroot -fakestat -afsdb\"\n\nConfiguration files\n-------------------\n\nAll of the command line values may be set in a configuration file. Place\nglobal configuration in `/etc/afsutil.cfg`, per user options in\n`~/.afsutil.cfg`, and per project options in `.git/afsutil.cfg`. Use command\nline options to override configuration options.\n\nThe **afsutil** configuration files are ini-style format. The sections of the\nconfiguration file correspond to the subcommand names, e.g., `build`,\n`install`, `newcell`. Options within each section correspond to the command\nline option names.\n\nSome subcommands, such as `install` and `newcell` have options like `--options`\nand `--paths`, which consist of multiple name/values pairs. These are\nrepresented in the configuration file as subsection in the form\n`[.