• Aucun résultat trouvé

STANDARDS CONFORMANCE cflow: SVID2, XPG2, XPG3

Dans le document HP-UX Reference (Page 176-184)

User Commands

STANDARDS CONFORMANCE cflow: SVID2, XPG2, XPG3

-ix -L -dnum

Reverse the "caller:callee" relationship producing an inverted listing shov"Ying the callers of each function. The listing is sorted in ascending collation order by callee (see Environment Variables below).

Include external and static data symbols. The default is to include only func-tions in the flowgraph.

Include names that begin with an underscore. The default is to exclude these functions (and data if -ix is used).

The num decimal integer indicates the depth at which the flowgraph is cut off.

By default this is a very large number. Attempts to set the cutoff depth to a nonpositive integer will be met with contempt.

DIAGNOSTICS

Complains about bad options. Complains about multiple definitions and only believes the first.

Other messages may come from the various programs used (e.g., the C-preprocessor).

DEPENDENCIES Series 300

The following option is supported:

- Y Enable support of 16-bit characters inside string literals and comments. Note that 8-bit parsing is always supported. See hpnls(S) for more details on International Support.

SEE ALSO

BUGS

as(l), cc(l), cpp(l), lex(l), lint(l), nm(l), pr(l), yacc(l).

Files produced by lex(1) and yacc(l) cause the reordering of line number declarations which can confuse cflow. To get proper results, feed cflow the yacc or lex input.

EXTERNAL INFLUENCES Environment Variables

LC_COLLATE determines the collating order output by the -r option.

If LCCOLLATE is not specified in the environment or is set to the empty string, the value of LANG is used as a default. If LANG is not specified or is set to the empty string, a default of

"C" (see lang(S» is used instead of LANG. If any internationalization variable contains an invalid setting, cflow behaves as if all internationalization variables are set to "C". See environ(5).

STANDARDS CONFORMANCE cflow: SVID2, XPG2, XPG3

154 (Section 1) - 2 - HP-UX Release 7.0: September 1989

CHACL(1) CHACL(1)

NAME

chad - add, modify, delete, copy, or summarize access control lists (ACLs) of files SYNOPSIS

chad ad file '"

chad -r ad file chad -d adpatt file chad -f fromfile tofile chad -[zIZIF] fiie ...

Remarks:

To ensure continued conformance with emerging industry standards, features described in this manual entry are likely to change in a future release.

DESCRIPTION

Chad extends the capabilities of chmod(1), by enabling the user to grant or restrict file access to additional specific users and/or groups. Traditional file access permissions, set when a file is created, grant or restrict access to the file's owner, group, and other users. Chad enables a user to designate up to thirteen additional sets of permissions (called optional access control list (ACL) entries) which are stored in the access control list of the file.

To use chad, the owner (or superuser) constructs an ad, a set of (user.group, mode) mappings to associate with one or more files. A specific user and group can be referred to by either name or number; any user (u), group (g), or both can be referred to with a % symbol, representing no specific user or group. The person executing the command can refer to the file's owner or group using the @ symbol.

Read, write, and execute/search (rwx) modes are identical to those used by chmod; symbolic operators (op) add (+), remove (-), or set (=) access rights. The entire ad should be quoted if it contains whitespace or special characters. Although two variants for constructing the ad are available (and fully explained in ad(S», the following syntax is suggested:

entry[, entry] ...

where the syntax for an entry is u.g op mode lop mode] ...

By default, chad modifies existing ACLs. It adds ACL entries or modifies access rights in exist-ing ACL entries. If ad contains an ACL entry already associated with a file, the entry's mode bits are changed to the new value given, or are modified by the specified operators. If the file's ACL does not already contain the specified entry, that ACL entry is added. Chad can also remove all access to files. Giving it a null ad argument means either "no access" (when using the -r option) or "no changes."

For a summary of the syntax, run chad without arguments.

If file is specified as -, chad operates on the file open as standard input.

Options

-r Replace old ACLs with the given ACL. All optional ACL entries are first deleted from the specified files's ACLs, their base permissions are set to zero, and the new ACL is applied. If ad does not contain an entry for the owner (u.%), the group (%.g), or the other (%.%) users of a file, that base ACL entry's mode is set to zero (no access). The command affects all of the file's ACL entries, but does not change the file's owner or group 10.

In chmod(1), the "modify" and "replace" operations are distinguished by the syntax (string or octal value). There is no corollary for ACLs because they have a variable number of entries. Hence chad modifies specific entries by default,

CHACL(l) updates each file's ACL only if entries are deleted from it.

If you attempt to delete a base ACL entry from any file, the entry remains but

Delete ("zap") all optional entries in the specified file's ACLs, leaving only base entries.

Delete ("zap") all optional entries in the specified file's ACLs, and set the access modes in all base entries to zero (no access). This is identical to replacing the old ACL with a null ACL:

chad -r " file ...

or using chmod(l), which deletes optional entries as a side effect:

chmod 0 file ...

Incorporate ("fold") optional ACL entries into base ACL entries. The base ACL entry's permission bits are altered, if necessary, to reflect the caller's effective access rights to the file; all optional entries, if any, are deleted.

For ordinary users, only the access mode of the owner base ACL entry can be altered. Unlike getaccess(l), the write bit is not turned off for a file on a read-only file system or a shared-text program being executed.

For superusers, only the execute mode bit in the owner base ACL entry might

Using @ in acl to represent "file owner or group" might cause chacl to run more slowly because it must reparse the ACL for each file (except with the -d option).

CHATR(l)

NAME

chatr - change program's internal attributes SYNOPSIS

chalr [-n] [-q] [-8] file ...

DESCRIPTION

CHATR(1)

Chatr, by default, prints each file's magic number and file attributes to the standard output.

\A/ith one or more optional arguments, chatr performs the follovving operations:

-n Change file from demand loaded to shared.

-q Change file from shared to demand loaded.

-s Perform its operation silently.

Upon completion, chatr prints the file's old and new values to standard output unless -8 is specified.

RETURN VALUE

Chatr returns zero on success. If the call to chatr is syntactically incorrect, or one or more of the specified files cannot be acted upon, chatr returns the number of files whose attributes could not be modified. If no files are specified, chatr returns decimal 255.

DIAGNOSTICS

The error messages produced by chatr are self-explanatory.

AUTHOR

Chatr was developed by HP.

SEE ALSO

Id(l), a.out(4), magic(4).

CHECKNR(1) CHECKNR(l)

NAME

checknr - check nroff/troff files SYNOPSIS

checknr [ -8 ] [ -f ] [ -a.xl.yl.x2.y2 ... xn.yn

1 [

-c.xl.x2.x3 .... xn

1 [

file ... ] DESCRIPTION

Checknr checks a list of nraff(l) or traff input files for certain kinds of errors involving mismatched opening and closing delimiters and unknown commands. If no files are specified, checknr checks the standard input. Delimiters checked are:

(1) Font changes using \fx ...

\fP.

(2) Size changes using \sx ... \sO.

(3) Macros that come in open ... close forms, such as the .TS and .TE macros, both of which must appear.

Checknr knows about the ms and me macro packages.

Additional pairs of macros can be added to the list using the -a option. This must be followed by groups of six characters, each group defining a pair of macros. The six characters are a period, the first macro name, another period, and the second macro name. For example, to define a pair .BS and .ES, use

-a.BS.ES

The -c option defines commands that checknr would interpret otherwise as ~ndefined.

The -£ option requests checknr to ignore \f font changes.

The -s option requests checknr to ignore \s size changes.

DIAGNOSTICS

Checknr complains about unmatched delimiters, unrecognized commands, and bad syntax of commands.

EXAMPLES

The command:

checknr -£ sorting

checks the file sorting for errors that involve mismatched opening and closing delimiters and unknown commands, but disregards errors caused by font changes.

WARNINGS

Checknr is intended for use on documents prepared with checknr in mind, much the same as lint. It expects a certain document writing style for \f and \s commands, in which each \fx is terminated with

\fP

and each \sx is terminated with \sO. While text formats properly when the next font or point size is specified instead of

\fP

or \sO, such practice produces complaints from checknr. If the user intends to run checknr, the

\fP

and \sO delimiting conventions should be used.

There is no way to define a single-character macro name using -a.

Checknr does not recognize certain reasonable constructs, such as conditionals.

AUTHOR

Checknr was developed by the University of California, Berkeley.

SEE ALSO

checkeq(l), lint(l), nroff(l).

EXTERNAL INFLUENCES

160 (Section 1) - 1 - HP-UX Release 7.0: September 1989

CHECKNR(l) CHECKNR(l)

International Code Set Support

Single-byte character code sets are supported.

CHFN(l) CHFN(l)

NAME

chfn - change finger entry SYNOPSIS

chfn [ loginname ] DESCRIPTION

Chfn is used to change information about users. This information is used by the finger(l) pro-gram, among others. It consists of the user's IIreal life ll name, location, office phone number, and home phone number. Chfn prompts the user for each field. Included in the prompt is a default value, which is enclosed in brackets. The default value is accepted simply by typing

<return>. To enter a blank field, type the word IInone ll . Below is a sample run:

Name [Tracy Simmons]:

Location (Ex: 47U-P5) []: 42L-P1 Office Phone (Ex: 1632) []: 1863

Home Phone (Ex: 9875432) [5551546]: none

Chfn allows phone numbers to be entered with or without hyphens.

It is a good idea to run finger(l) after running chfn to make sure everything is the way you want it.

The optional argument loginname is used to change another person's finger(l) information. This can only be done by the superuser.

WARNINGS

The encoding of the office and extension information is installation dependent.

For historical reasons, the user's name, etc., are stored in the passwd file. This is an inap-propriate place to store the information.

Because two users may try to write the passwd file at once, a synchronization method was developed. On rare occasions, a message that the password file is IIbusyll will be printed. In this case, chfn sleeps for a while and then tries to write to the passwd file again.

AUTHOR

Chfn was developed by the University of California, Berkeley.

FILES

/etc/passwd /etc/ptmp SEE ALSO

finger(l), passwd(4).

162 (Section 1) - 1 - HP-UX Release 7.0: September 1989

CHMOD(1) CHMOD(1) default, in conformance with the IEEE Standard POSIX 1003.1-1988, optional ACL entries are deleted.) For information about access control lists, see acl(5).

The permissions of any named file are changed according to mode, which can be absolute or per-mission absolutely (all other bits will be reset).

Permission is any combination of the letters r (read), w (write), x (execute), s (set owner or group ID), H (hide directory), and t (save text or sticky); u, g or 0 indicate that permission is to be taken from the current mode. Omitting permission is only useful with = to take away all permissions.

Multiple symbolic modes separated by commas can be given. Operations are performed in the order specified. The letter s is only useful with u or g and t only works with u.

CHMOD(1) CHMOD(1)

Only the owner of a file (or the super-user) can change its mode. Only the super-user can set the sticky bit. In order to set the group ID, the group of the file must correspond to your current group ID.

When using chmod on a symbolic link, the mode of the file referred to by the link is changed.

RETURN VALUE

Dans le document HP-UX Reference (Page 176-184)