1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=Windows-1252">
<title>AKLOG Command</title>
</head>
<body bgcolor="#ffffff" text="#000000">
<object type="application/x-oleobject"
classid="clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e"> <param
name="Keyword" value="kinit, man">
</object>
<p><h2><a name="id_help_kinit"></a>AKLOG Command</h2></p>
<p>(from UNIX man page)</p>
<pre><code>User Commands AKLOG(1)<br><br>NAME<br> aklog - Obtain tokens for authentication to AFS<br><br>SYNOPSIS<br> aklog [ -d ] [ -force ] [ -hosts ] [ -zsubs ] [ -noprdb ] [<br> [ -cell | -c ] cell [ -k kerberos-realm ] ] [ [ -path | -p ]<br> pathname ]<br><br>DESCRIPTION<br> The aklog program is used to authenticate to a cell or<br> directory in AFS, the Andrew Filesystem, by obtaining AFS<br> tokens. Ordinarily, aklog is not used directly but called by<br> attach(1).<br><br> If aklog is invoked with no command line arguments, it will<br> obtain tokens for the workstation's local cell. It is pos-<br> sible to invoke aklog with arbitrarily many cells and path-<br> names specified on the command line. aklog knows how to<br> expand cell name abbreviations, so short forms of cell names<br> can be use used. In addition, aklog understands the follow-<br> ing command line options:<br><br> -cell | -c cell<br> This flag is not ordinarily necessary since aklog can<br> usually figure out when an argument is a cell. It can<br> be used to introduce a cell name that would ordinarily<br> be mistaken for a path name if this should be required.<br> If this flag is omitted, an argument will be treated as<br> a cell name if it contains no slashes (/) and is neither<br> "." nor ".." .<br><br> -k kerberos-realm<br> This flag is valid only when immediately following the<br> name of a cell. It is used to tell aklog what kerberos<br> realm should be used while authenticating to the preced-<br> ing cell. This argument is unnecessary except when the<br> workstation is not properly configured. Ordinarily,<br> aklog can determine this information on its own.<br><br> -path | -p pathname<br> Like the -cell flag, this flag is usually unnecessary.<br> When it appears, the next command line argument is<br> always treated as a path name. Ordinarily, an argument<br> is treated as a path name if it is "." or ".." or if it<br> contains a slash (/).<br><br> -hosts<br> Prints all the server addresses which may act as a sin-<br> gle point of failure in accessing the specified direc-<br> tory path. Each element of the path is examined, and as<br> new volumes are traversed, if they are not replicated,<br> the server's IP address containing the volume will be<br> displayed. Attach(1) invokes aklog with this option.<br> The output is of the form<br><br> host: IP address<br><br> -zsubs<br> Causes the printing of the zephyr subscription informa-<br> tion that a person using a given path or cell would<br> want. Attach(1) invokes aklog with this option. The<br> output is of the form<br><br> zsub: instance<br><br> where instance is the instance of a class filsrv zephyr<br> subscription.<br><br> -noprdb<br> Ordinarily, aklog looks up the AFS ID corresponding to<br> the name of the person invoking the command. Specifying<br> this flag turns off this functionality. This may be<br> desirable if the protection database is unavailable for<br> some reason and tokens are desired anyway.<br><br> -d Turns on printing of debugging information. This option<br> is not intended for general users.<br><br> -force<br> Forces aklog to obtain new tokens even if the user<br> already appears to have tokens identical to the new ones<br> they would get. This option is most often required when<br> the user has recently been added to an AFS group.<br><br>EXIT CODES<br> The exit status of aklog will be one of the following:<br><br> 0 Success -- No error occurred.<br><br> 1 Usage -- Bad command syntax; accompanied by a usage<br> message.<br><br> 2 Something failed -- More than one cell or pathname was<br> given on the command line and at least one failure<br> occurred. A more specific error status is returned<br> when only one directive is given.<br><br> 3 AFS -- Unable to get AFS configuration or unable to get<br> information about a specific cell.<br><br> 4 Kerberos -- Unable to get tickets for authentication.<br><br> 5 Token -- Unable to get tokens.<br><br> 6 Bad pathname -- The path given was not a directory or<br> lstat(2) failed on some component of the pathname.<br><br> 7 Miscellaneous -- An internal failure occurred. For<br> example, aklog returns this if it runs out of memory.<br><br>EXAMPLES<br> To get tokens for the local cell:<br> % aklog<br><br> To get tokens for the athena.mit.edu cell:<br> % aklog athena.mit.edu<br> or<br> % aklog athena<br><br> To get tokens adequate to read<br> /afs/athena.mit.edu/user/p/potato:<br> % aklog /afs/athena.mit.edu/user/p/potato<br><br> To get tokens for a test cell that is in a test Kerberos<br> realm:<br> % aklog testcell.mit.edu -k TESTREALM.MIT.EDU<br><br>SEE ALSO<br> attach(1), tokens(1), unlog(1)<br><br><br></code></pre>
</body>
</html>
|
