1SACT(1P)                   POSIX Programmer's Manual                  SACT(1P)
2
3
4

PROLOG

6       This  manual  page is part of the POSIX Programmer's Manual.  The Linux
7       implementation of this interface may differ (consult the  corresponding
8       Linux  manual page for details of Linux behavior), or the interface may
9       not be implemented on Linux.
10

NAME

12       sact - print current SCCS file-editing activity (DEVELOPMENT)
13

SYNOPSIS

15       sact file...
16

DESCRIPTION

18       The sact utility shall inform the user of any  impending  deltas  to  a
19       named  SCCS  file by writing a list to standard output.  This situation
20       occurs when get -e has been executed previously  without  a  subsequent
21       execution of delta, unget, or sccs unedit.
22

OPTIONS

24       None.
25

OPERANDS

27       The following operand shall be supported:
28
29       file   A pathname of an existing SCCS file or a directory. If file is a
30              directory, the sact utility shall behave as though each file  in
31              the  directory  were specified as a named file, except that non-
32              SCCS files (last component of the pathname does not  begin  with
33              s.) and unreadable files shall be silently ignored.
34
35       If  exactly one file operand appears, and it is '-', the standard input
36       shall be read; each line of the standard input shall be taken to be the
37       name  of  an  SCCS file to be processed.  Non-SCCS files and unreadable
38       files shall be silently ignored.
39
40

STDIN

42       The standard input shall be a text file used only when the file operand
43       is  specified  as '-' . Each line of the text file shall be interpreted
44       as an SCCS pathname.
45

INPUT FILES

47       Any SCCS files interrogated are files of an unspecified format.
48

ENVIRONMENT VARIABLES

50       The following environment variables shall affect the execution of sact:
51
52       LANG   Provide a default value for the  internationalization  variables
53              that  are  unset  or  null.  (See the Base Definitions volume of
54              IEEE Std 1003.1-2001, Section  8.2,  Internationalization  Vari‐
55              ables  for the precedence of internationalization variables used
56              to determine the values of locale categories.)
57
58       LC_ALL If set to a non-empty string value, override the values  of  all
59              the other internationalization variables.
60
61       LC_CTYPE
62              Determine  the  locale  for  the  interpretation of sequences of
63              bytes of text data as characters (for  example,  single-byte  as
64              opposed to multi-byte characters in arguments and input files).
65
66       LC_MESSAGES
67              Determine  the  locale  that should be used to affect the format
68              and contents of diagnostic messages written to standard error.
69
70       NLSPATH
71              Determine the location of message catalogs for the processing of
72              LC_MESSAGES .
73
74

ASYNCHRONOUS EVENTS

76       Default.
77

STDOUT

79       The output for each named file shall consist of a line in the following
80       format:
81
82
83              "%s %s %s %s %s\n", <SID>, <new SID>, <login>, <date>, <time>
84
85       <SID>  Specifies the SID of a delta that currently exists in  the  SCCS
86              file to which changes are made to make the new delta.
87
88       <new SID>
89              Specifies the SID for the new delta to be created.
90
91       <login>
92              Contains  the  login  name of the user who makes the delta (that
93              is, who executed a get for editing).
94
95       <date> Contains the date that get -e was executed, in the  format  used
96              by the prs :D: data keyword.
97
98       <time> Contains  the  time that get -e was executed, in the format used
99              by the prs :T: data keyword.
100
101
102       If there is more than one named file or  if  a  directory  or  standard
103       input  is named, each pathname shall be written before each of the pre‐
104       ceding lines:
105
106
107              "\n%s:\n", <pathname>
108

STDERR

110       The standard error shall be used only for optional informative messages
111       concerning SCCS files with no impending deltas, and for diagnostic mes‐
112       sages.
113

OUTPUT FILES

115       None.
116

EXTENDED DESCRIPTION

118       None.
119

EXIT STATUS

121       The following exit values shall be returned:
122
123        0     Successful completion.
124
125       >0     An error occurred.
126
127

CONSEQUENCES OF ERRORS

129       Default.
130
131       The following sections are informative.
132

APPLICATION USAGE

134       None.
135

EXAMPLES

137       None.
138

RATIONALE

140       None.
141

FUTURE DIRECTIONS

143       None.
144

SEE ALSO

146       delta, get, sccs, unget
147
149       Portions of this text are reprinted and reproduced in  electronic  form
150       from IEEE Std 1003.1, 2003 Edition, Standard for Information Technology
151       -- Portable Operating System Interface (POSIX),  The  Open  Group  Base
152       Specifications  Issue  6,  Copyright  (C) 2001-2003 by the Institute of
153       Electrical and Electronics Engineers, Inc and The Open  Group.  In  the
154       event of any discrepancy between this version and the original IEEE and
155       The Open Group Standard, the original IEEE and The Open Group  Standard
156       is  the  referee document. The original Standard can be obtained online
157       at http://www.opengroup.org/unix/online.html .
158
159
160
161IEEE/The Open Group                  2003                             SACT(1P)
Impressum