sccs-sact(1) | User Commands | sccs-sact(1) |
sccs-sact, sact - show editing activity status of an SCCS file
/usr/ccs/bin/sact [-s] [-N bulk-spec] s.filename...
The sact utility informs the user of any SCCS files that are checked out for editing.
The output for each named file consists of five fields separated by SPACE characters.
If a directory name is used in place of the s.filename argument, the sact command applies to all s.files in that directory. Unreadable s.files produce an error; processing continues with the next file (if any). The use of `−' as the s.filename argument indicates that the names of files are to be read from the standard input, one s.file per line.
The bulk-spec parameter is composed from an optional list of flag parameters followed by an optional path specifier.
The following flag types are supported:
The following path specifier types are supported:
A typical value for dir is SCCS.
In order to overcome the limited number of exec(2) arguments, it is recommended to use `−' as the file name parameter for sccslog(1) and to send a list of path names to stdin.
See environ(5) for descriptions of the following environment variables that affect the execution of sact(1): LANG, LC_ALL, LC_COLLATE, LC_CTYPE, LC_MESSAGES, and NLSPATH.
The following exit values are returned:
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
Availability | SUNWsprot |
Interface Stability | Standard |
sccs(1), sccs-admin(1), sccs-cdc(1), sccs-comb(1), sccs-cvt(1), sccs-delta(1), sccs-get(1), sccs-help(1), sccs-log(1), sccs-prs(1), sccs-prt(1), sccs-rmdel(1), sccs-sccsdiff(1), sccs-unget(1), sccs-val(1), bdiff(1), diff(1), what(1), sccschangeset(4), sccsfile(4), attributes(5), environ(5), standards(5).
Use the SCCS help command for explanations (see sccs-help(1)).
The SCCS suite was originally written by Marc J. Rochkind at Bell Labs in 1972. Release 4.0 of SCCS, introducing new versions of the programs admin(1), get(1), prt(1), and delta(1) was published on February 18, 1977; it introduced the new text based SCCS v4 history file format (previous SCCS releases used a binary history file format). The SCCS suite was later maintained by various people at AT&T and Sun Microsystems. Since 2006, the SCCS suite is maintained by Joerg Schilling.
A frequently updated source code for the SCCS suite is included in the schilytools project and may be retrieved from the schilytools project at Sourceforge at:
http://sourceforge.net/projects/schilytools/
The download directory is:
http://sourceforge.net/projects/schilytools/files/
Check for the schily-*.tar.bz2 archives.
Less frequently updated source code for the SCCS suite is at:
http://sourceforge.net/projects/sccs/files/
Separate project informations for the SCCS project may be retrieved from:
http://sccs.sf.net
2018/12/18 | SunOS 5.11 |