sact(1) sact(1)NAME sact - display who has checked an SCCS file out for editing. SYNOPSIS sact file ... DESCRIPTION sact informs the user of any impending deltas to a named SCCS file. This situation occurs when get(1) with the -e flag option has been previously executed without a subse- quent execution of delta(1). If a directory is named on the command line, sact behaves as though each file in the direc- tory were specified as a named file, except that non-SCCS files and unreadable files are silently ignored. If a name of - is given, the standard input is read with each line be- ing taken as the name of an SCCS file to be processed. The output for each named file consists of five fields separated by spaces. Field 1 specifies the SID of a delta that currently exists in the SCCS file to which changes will be made to make the new delta. Field 2 specifies the SID for the new delta to be created. Field 3 contains the logname of the user who will make the delta (i.e., executed a get for editing). Field 4 contains the date that get -e was executed. Field 5 contains the time that get -e was executed. EXAMPLES If the user has done a get -e, but not a delta to merge the new changes, doing a sact s.test1.c would show: 1.2 1.3 virginia 82/11/10 16:10:35 indicating that a new version numbered 1.3 is in the process of being made from version numbered 1.2 by user virginia. The get -e for the file was done on 82/11/10 at 16:10:35. FILES /usr/bin/sact April, 1990 1
sact(1) sact(1)SEE ALSO admin(1), cdc(1), comb(1), delta(1), get(1), help(1), prs(1), rmdel(1), sccs(1), sccsdiff(1), unget(1), val(1), what(1), sccsfile(4). ``SCCS Reference'' in A/UX Programming Languages and Tools, Volume 2. DIAGNOSTICS Use help(1) for explanations. 2 April, 1990