mirror of
https://git.openafs.org/openafs.git
synced 2025-01-18 06:50:12 +00:00
3b605e621f
On AIX, there are two kernel extensions, and each is loaded by a utility in src/export, cfgexport, and cfgafs. This utility calls the AIX "sysconfig" system call to load the extension into the kernel. Historically this usually works so error messages are not often seen, though the programs have facilities to display error messages. Error messages from the loading of kernel extensions are displayed using the execerror utility. Beginning with AIX 4.2, this utility was moved from /etc/execerror to /usr/sbin. The AFS cfg utlities were never updated. If an error occurs during loading of one of the extensions, the user receives the following misleading error: SYS_KLOAD: No such file or directory This error is not actually the result of the failed extension load, but actually the result of the next source code line: perror("SYS_KLOAD"); This error is actually a statement that the utility cannot find execerror. Update the utilities to call execerror from the correct location starting with AIX 4.2. Change-Id: I91bf7d93c35d536c9b3ad0f97f02c5a0289cbf63 Reviewed-on: https://gerrit.openafs.org/16006 Tested-by: BuildBot <buildbot@rampaginggeek.com> Reviewed-by: Ben Huntsman <ben@huntsmans.net> Reviewed-by: Cheyenne Wills <cwills@sinenomine.net> Reviewed-by: Michael Meffie <mmeffie@sinenomine.net> Reviewed-by: Mark Vitale <mvitale@sinenomine.net> Reviewed-by: Andrew Deason <adeason@sinenomine.net> |
||
---|---|---|
build-tools | ||
doc | ||
src | ||
tests | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.splintrc | ||
acinclude.m4 | ||
CODING | ||
configure-libafs.ac | ||
configure.ac | ||
CONTRIBUTING | ||
INSTALL | ||
libafsdep | ||
LICENSE | ||
Makefile-libafs.in | ||
Makefile.in | ||
NEWS | ||
NTMakefile | ||
README | ||
README-WINDOWS | ||
regen.sh |
AFS is a distributed file system that enables users to share and access all of the files stored in a network of computers as easily as they access the files stored on their local machines. The file system is called distributed for this exact reason: files can reside on many different machines, but are available to users on every machine. OpenAFS 1.0 was originally released by IBM under the terms of the IBM Public License 1.0 (IPL10). For details on IPL10 see the LICENSE file in this directory. The current OpenAFS distribution is licensed under a combination of the IPL10 and many other licenses as granted by the relevant copyright holders. The LICENSE file in this directory contains more details, thought it is not a comprehensive statement. See INSTALL for information about building and installing OpenAFS on various platforms. See CODING for developer information and guidelines. See NEWS for recent changes to OpenAFS.