1 .\" $Id: kafs.3,v 1.8 2002/08/28 20:04:31 joda Exp $
11 .Nm k_afs_cell_of_file ,
15 .\" .Nm krb5_afslog_uid
18 AFS cache manager access library (libkafs, -lkafs)
22 .Fn k_afs_cell_of_file "const char *path" "char *cell" "int len"
26 .Fn k_pioctl "char *a_path" "int o_opcode" "struct ViceIoctl *a_paramsP" "int a_followSymlinks"
32 .Fn krb_afslog "char *cell" "char *realm"
34 .Fn krb_afslog_uid "char *cell" "char *realm" "uid_t uid"
35 .\" .Ft krb5_error_code
36 .\" .Fn krb5_afslog_uid "krb5_context context" "krb5_ccache id" "const char *cell" "krb5_const_realm realm" "uid_t uid"
37 .\" .Ft krb5_error_code
38 .\" .Fn krb5_afslog "krb5_context context" "krb5_ccache id" "const char *cell" "krb5_const_realm realm"
41 initializes some library internal structures, and tests for the
42 presence of AFS in the kernel, none of the other functions should be
45 is called, or if it fails.
50 obtains new tokens (and possibly tickets) for the specified
58 the local cell is used. If
62 the function tries to guess what realm to use. Unless you have some good knowledge of what cell or realm to use, you should pass
65 will use the real user-id for the
74 .\" .Fn krb5_afslog_uid
75 .\" are the Kerberos 5 equivalents of
78 .\" .Fn krb_afslog_uid .
79 .\" The extra arguments are the ubiquitous context, and the cache id where
80 .\" to store any obtained tickets. Since AFS servers normally can't handle
81 .\" Kerberos 5 tickets directly, these functions will first obtain version
82 .\" 5 tickets for the requested cells, and then convert them to version 4
83 .\" tickets, that can be stashed in the kernel. To convert tickets the
84 .\" .Fn krb524_convert_creds_kdc
85 .\" function will be used.
87 .Fn k_afs_cell_of_file
90 return the cell of a specified file, no more than
98 syscall with the specified arguments. This function is equivalent to
102 initializes a new PAG.
105 removes destroys all tokens in the current PAG.
108 returns 1 if AFS is present in the kernel, 0 otherwise.
112 returns 0 on success, or a kerberos error number on failure.
113 .Fn k_afs_cell_of_file ,
118 all return the value of the underlaying system call, 0 on success.
120 The following environment variable affect the mode of operation of
122 .Bl -tag -width AFS_SYSCALL
126 will try to figure out the correct system call(s) that are used by AFS
127 by itself. If it does not manage to do that, or does it incorrectly,
128 you can set this variable to the system call number or list of system
129 call numbers that should be used.
132 The following code from
134 will obtain a new PAG and tokens for the local cell and the cell of
135 the users home directory.
140 if(k_afs_cell_of_file(pwd->pw_dir, cell, sizeof(cell)) == 0)
141 krb_afslog(cell, NULL);
142 krb_afslog(NULL, NULL);
146 If any of these functions (apart from
148 is called without AFS beeing present in the kernel, the process will
149 usually (depending on the operating system) receive a SIGSYS signal.
152 .%A Transarc Corporation
153 .%J AFS-3 Programmer's Reference
154 .%T File Server/Cache Manager Interface
159 has no effect under AIX.