HP UX Operating Systems 44

admin(1)

environ(5).

International Code Set Support

Single-byte and multi-byte character code sets are supported.

DIAGNOSTICS

Use sccshelp(1) for explanations.

WARNINGS

SCCS ®les can be any length, but the number of lines in the text ®le itself cannot exceed 99 999 lines.

FILES

The last component of all SCCS ®le names must be of the form s.®lename. New SCCS ®les are given mode 444 (see chmod(1)). Write permission in the pertinent directory is required to create a ®le. All writing done by admin is to a temporary x-®le, called x.®lename, (see get(1)), created with mode 444 if the admin command is creating a new SCCS ®le, or with the same mode as the SCCS ®le if it exists. After successful execution of admin, the SCCS ®le is removed (if it exists), and the x-®le is renamed to the name of the SCCS ®le. This ensures that changes are made to the SCCS ®le only if no errors occurred.

It is recommended that directories containing SCCS ®les be mode 755 and that SCCS ®les themselves be mode 444. The mode of any given directory allows only the owner to modify SCCS ®les contained in that directory. The mode of the SCCS ®les prevents any modi®cation at all except by SCCS commands.

If it should be necessary to patch an SCCS ®le for any reason, the mode can be changed to 644 by the owner, thus allowing the use of vi or any other suitable editor. Care must be taken! The edited ®le should always be processed by an admin -hto check for corruption followed by an admin -zto generate a proper checksum. Another admin -his recommended to ensure the SCCS ®le is valid.

admin also makes use of a transient lock ®le called z.®lename), which is used to prevent simultaneous updates to the SCCS ®le by different users. See get(1) for further information.