be selected by defining a symbol, which, if not defined, leaves the
program exactly as it was before the changes.
* Although it might be possible to "clean up" the "#ifdef mess",
- nobody has accesss to all the hundreds of platforms served by the
+ nobody has access to all the hundreds of platforms served by the
#ifdefs to check the results.
And to answer the second-most-oft-repeated question: "Why don't you
calling and return conventions, and has the same type.
The Group E modules contain both functions and global variables that
- are accesssed by modules in the other groups. These are now described.
+ are accessed by modules in the other groups. These are now described.
(By the way, I got this list by linking all the C-Kermit modules
together except ckutio and ckufio. These are the symbols that ld
char *dftty;
Default communication device. Set by Group E module. Used in
- many places. This variable should be initialized the the symbol
+ many places. This variable should be initialized the symbol
CTTNAM, which is defined in ckcdeb.h, e.g. as "/dev/tty" for
UNIX, "TT:" for VMS, etc. Example: char *dftty = CTTNAM;
#define ZSYSFN 8 /* Input from a system function (pipe) */
#define ZRFILE 9 /* Local file for READ command */ (NEW)
#define ZWFILE 10 /* Local file for WRITE command */ (NEW)
- #define ZMFILE 11 /* Auxilliary file for internal use */ (NEW)
+ #define ZMFILE 11 /* Auxiliary file for internal use */ (NEW)
#define ZNFILS 12 /* How many defined file numbers */
In the descriptions below, fn refers to a filename, and n refers to one
Check to see if file with name fn is a regular, readable,
existing file, suitable for Kermit to send -- not a directory,
not a symbolic link, etc. Returns:
- -3: if file exists but is not accesssible (e.g.
- read-protected);
+ -3: if file exists but is not accessible (e.g. read-protected);
-2: if file exists but is not of a readable type (e.g. a
directory);
-1: on error (e.g. file does not exist, or fn is garbage);
long
zgetfs(fn) char *fn;
- Gets the size of the given file, regardless of accesssibility.
+ Gets the size of the given file, regardless of accessibility.
Used for directory listings. Unlike zchki(), should return the
size of any kind of file, even a directory. zgetfs() also should
serve as a mini "get file info" function that can be used until
int
zsetroot(char * dir)
- Sets the root for the user's file accesss, like Unix chroot(),
+ Sets the root for the user's file access, like Unix chroot(),
but does not require privilege. In Unix, this must be
- implemented entirely by Kermit's own file accesss routines.
+ implemented entirely by Kermit's own file access routines.
Returns:
1: Success
-1: Invalid argument
int
zxcmd(n,s) char *s;
- Runs a system command so its output can be accesssed as if it
+ Runs a system command so its output can be accessed as if it
were file n. The command is run in ordinary, unprivileged user
mode.
If n is ZSTDIO or ZCTERM, returns -1.
isn't. Makes any appropriate system log entries (IKSD logins,
failed login attempts, etc). If password is valid, logs the user
in as herself (if real user), or sets up restricted anonymous
- accesss if user is guest (e.g. changes file-system root to
+ access if user is guest (e.g. changes file-system root to
anonroot and sets isguest = 1).
VOID
installed to prevent such security breaches by turning off the
program's special privileges at all times except when they are needed.
- In UNIX, the only need Kermit has for privileged status is accesss to
+ In UNIX, the only need Kermit has for privileged status is access to
the UUCP lockfile directory, in order to read, create, and destroy
lockfiles, and to open communication devices that are normally
protected against the user (see the [133]Unix C-Kermit Installation
Instructions for discussion). Therefore, privileges should only be
enabled for these operations and disabled at all other times. This
relieves the programmer of the responsibility of putting expensive and
- unreliable accesss checks around every file accesss and subprocess
+ unreliable access checks around every file access and subprocess
creation.
Strictly speaking, these functions are not required in all C-Kermit
Attempts to turns privileges off in such a way that they can be
turned on again later. Then checks to make sure that they were
really turned off. If they were not really turned off, then they
- are cancelled permanently. Returns:
+ are canceled permanently. Returns:
0 on success
nonzero on failure
int
ttclos()
Closes the communication device (tty or network). If there were
- any kind of exclusive accesss locks connected with the tty,
- these are released. If the tty has a modem connection, it is
- hung up. For true tty devices, the original tty device modes are
+ any kind of exclusive access locks connected with the tty, these
+ are released. If the tty has a modem connection, it is hung up.
+ For true tty devices, the original tty device modes are
restored. Returns:
-1: on failure.
0: on success.
<=0: no timer, wait forever (e.g. for incoming
call).
For real tty devices, ttopen() attempts to gain
- exclusive accesss to the tty device, for example in
+ exclusive access to the tty device, for example in
UNIX by creating a "lockfile" (in other operating
- systems, like VMS, exclusive accesss probably
+ systems, like VMS, exclusive access probably
requires no special action).
Side effects:
Returns:
0: on success
-5: if device is in use
- -4: if accesss to device is denied
- -3: if accesss to lock mechanism denied
+ -4: if access to device is denied
+ -3: if access to lock mechanism denied
-2: upon timeout waiting for device to open
-1: on other error
For UNIX (System ID = U1), it's the familiar 3-digit octal number, the
low-order 9 bits of the filemode: Owner, Group, World, e.g. 660 =
- read/write accesss for owner and group, none for world, recorded as a
+ read/write access for owner and group, none for world, recorded as a
3-digit octal string. High-order UNIX permission bits are not
transmitted.
projects / ckermit.git / blobdiff