16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Usage notes<br />

Related Information<br />

inetd<br />

provides the user connection to the socket, and the second is the user’s<br />

shell. In this mode, all shell functions behave in a manner conformant to the<br />

standards.<br />

If you specify –m, the rlogin process and the shell process share the same<br />

address space using z/<strong>OS</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> support for multiple<br />

processes in an address space. Using –m has the potential of doubling the<br />

number of users supported via rlogin.<br />

Note: If you issued rlogind with the –m option, the shell process cannot<br />

execute a setuid program that replaces the shell. This causes<br />

functions like newgrp to fail. In this situation, you may want to create<br />

a secondary shell that runs in its own address space.<br />

–n Specifies that the transport-level keep-alive messages be disabled. The<br />

messages are enabled by default.<br />

1. The rlogind program normally translates all error and warning messages to<br />

ASCII and then sends them to the originating terminal.<br />

However, when the C runtime library writes error messages, the rlogind<br />

program cannot intercept them to translate the messages to ASCII. Therefore,<br />

these messages are written to the file /tmp/rlogind.stderr or<br />

/tmp/rlogind2.stderr.<br />

These two files must be predefined in /tmp, and owned by the superuser (UID<br />

0). The files should have permissions of rw–rw–rw or rw––w––w–. In addition,<br />

the sticky bit must be set for the /tmp directory so that these files (and other<br />

files in /tmp) cannot be removed except by the files’ owners or the superuser.<br />

2. rlogind is not affected by the locale information specified in locale-related<br />

environment variables.<br />

rm — Remove a directory entry<br />

Format<br />

Description<br />

rm [–fiRrv] file ...<br />

rlogind<br />

rm removes files (provided that it is a valid pathname). If you specify either . or ..<br />

as the final component of the pathname for a file, rm displays an error message<br />

and goes to the next file. If a file does not have write permission set, rm asks you if<br />

you are sure you want to delete the file; type the yes expression defined in<br />

LC_MESSAGES (the English expression is typically y or yes) if you really want it<br />

deleted.<br />

Restriction: A file can be removed by any user who has write permission to the<br />

directory containing the file, unless that directory has its sticky bit turned on. If the<br />

file is in a directory whose sticky bit is turned on, only the file owner, the owner of<br />

the directory, or a superuser can remove the file.<br />

Chapter 2. Shell command descriptions 531

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!