11 .Nm k_afs_cell_of_file ,
15 \" .Nm krb5_afslog_uid
20 .Fn k_afs_cell_of_file "const char *path" "char *cell" "int len"
24 .Fn k_pioctl "char *a_path" "int o_opcode" "struct ViceIoctl *a_paramsP" "int a_followSymlinks"
30 .Fn krb_afslog "char *cell" "char *realm"
32 .Fn krb_afslog_uid "char *cell" "char *realm" "uid_t uid"
33 \" .Ft krb5_error_code
34 \" .Fn krb5_afslog_uid "krb5_context context" "krb5_ccache id" "const char *cell" "krb5_const_realm realm" "uid_t uid"
35 \" .Ft krb5_error_code
36 \" .Fn krb5_afslog "krb5_context context" "krb5_ccache id" "const char *cell" "krb5_const_realm realm"
39 initializes some library internal structures, and tests for the
40 presense of AFS in the kernel, none of the other functions should be
43 is called, or if it fails.
48 obtains new tokens (and possibly tickets) for the specified
56 the local cell is used. If
60 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
63 will use the real user-id for the
72 \" .Fn krb5_afslog_uid
73 \" are the Kerberos 5 equivalents of
76 \" .Fn krb_afslog_uid .
77 \" The extra arguments are the ubiquitous context, and the cache id where
78 \" to store any obtained tickets. Since AFS servers normally can't handle
79 \" Kerberos 5 tickets directly, these functions will first obtain version
80 \" 5 tickets for the requested cells, and then convert them to version 4
81 \" tickets, that can be stashed in the kernel. To convert tickets the
82 \" .Fn krb524_convert_creds_kdc
83 \" function will be used.
85 .Fn k_afs_cell_of_file
88 return the cell of a specified file, no more than
96 syscall with the specified arguments. This function is equivalent to
100 initializes a new PAG.
103 removes destroys all tokens in the current PAG.
106 The following environment variable affect the mode of operation of
112 will try to figure out the correct system call(s) that are used by AFS
113 by itself. If it does not manage to do that, or does it incorrectly,
114 you can set this variable to the system call number or list of system
115 call numbers that should be used.
119 returns 1 if AFS is present in the kernel, 0 otherwise.
123 returns 0 on success, or a kerberos error number on failure.
124 .Fn k_afs_cell_of_file ,
129 all return the value of the underlaying system call, 0 on success.
131 The following code from
133 will obtain a new PAG and tokens for the local cell and the cell of
134 the users home directory.
139 if(k_afs_cell_of_file(pwd->pw_dir, cell, sizeof(cell)) == 0)
140 krb_afslog(cell, NULL);
141 krb_afslog(NULL, NULL);
145 If any of these functions (appart from
147 is called without AFS beeing present in the kernel, the process will
148 usually (depending on the operating system) receive a SIGSYS signal.
151 .%A Transarc Corporation
152 .%J AFS-3 Programmer's Reference
153 .%T File Server/Cache Manager Interface
158 has no effect under AIX.