sccs-sact(1)

📦 version 2022.10.16, in opensuse-leap 16.0

💅 NAME 💅

sccs-sact, sact — show the editing activity status of an SCCS file. Yep bestie, we're in the sccs-sact(1) page, User Commands territory, buckle up 🎀

✨ SYNOPSIS ✨

/usr/ccs/bin/sact [-s]
    [-Xextended-options] [-Nbulk-spec] s.filename...

🦋 DESCRIPTION 🦋

okay so the sact utility is literally just vibes-checking your SCCS files — it tells you which ones are checked out for editing. that's it, that's the whole job 💅

The output for each named file is five fields, separated by SPACE characters:

  1. the SID of a delta that currently exists in the SCCS file, the one you'll be making changes to in order to make the new delta 🔥
  2. the SID for the new delta that's going to be created ✨
  3. the username of the person who has the file checked out for editing 👑
  4. the date the version was checked out 📅
  5. the time the version was checked out ⏰

If you pass a directory name instead of the s.filename argument, sact applies to all s.files in that directory. Unreadable s.files produce an error, but processing just keeps going with the next file (if there is one) — no cap, it does not give up on you 🫶

And if you use - as the s.filename argument, that means the names of the files are to be read from standard input, one s.file per line. cute, right? 🧚

🌸 OPTIONS 🌸

  • -s — suppresses the error message when a file is not currently edited. silence is golden 💜
  • -Nbulk-spec — processes a bulk of SCCS history files. This option lets you do an efficient mass processing of SCCS history files. mass processing, but make it efficient 😤

The bulk-spec parameter is composed of an optional list of flag parameters followed by an optional path specifier.

The following flag types are supported:

  • none

The following path specifier types are supported:

  • -N — the file name parameters to the sccslog command are not s.filename files but the names of the g-files. The s.filename names are automatically derived from the g-file names by prepending s. to the last path name component. Both the s.filename and the g-file are in the same directory.
  • -Ns. — the file name parameters to the sccslog command are s.filename files. The g-files names are automatically derived by removing s. from the beginning of the last path name component of the s.filename. Both the s.filename and the g-file are in the same directory.
  • -Ndir — the file name parameters to the sccslog command are not s.filename files but the names of the g-files. The s.filename names are put into directory dir, and the names are automatically derived from the g-file names by prepending dir/s. to the last path name component.
  • -Ndir/s. — the file name parameters to the sccslog command are s.filename files in directory dir. The g-files names are automatically derived by removing dir/s. from the beginning of the last path name component of the s.filename.

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. seriously, do it, your argv will thank you 🙏

  • -Xextended-options — specify extended options. The extended-options argument may be a comma separated list of extended option names.

The following extended options are supported, and they may be abbreviated as long as the abbreviation is still unique. Options with a parameter may not be abbreviated. noted 📝

  • 0 — when reading filenames from stdin, triggered by a file name argument -, the filename separator is a null byte instead of a newline. This allows you to use long lists with arbitrary filenames. long lists with arbitrary filenames?? obsessed 😭
  • help — print a short online help for available options.
bestie, the -X option is a SCHILY extension that does not exist in historic sccs implementations. it's giving "new gen only" 💅
  • -V, -version, --version — prints the sact version number string, and exists. (yes, that's what it says ✨)
another SCHILY extension that does not exist in historic sccs implementations 🌈

🌼 ENVIRONMENT VARIABLES 🌼

See environ(7) 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 whole alphabet soup of locales, iykyk 🌍

  • SCCS_NO_HELP — if set, sact(1) will not automatically call help(1) with the SCCS error code in order to print a more helpful error message. Scripts that depend on the exact error messages of SCCS commands should set the environment variable SCCS_NO_HELP and set LC_ALL=C. no vibes-based extra help for you, just raw error text 💀

⭐ EXIT STATUS ⭐

The following exit values are returned:

  • 0 — successful completion. slay 🎉
  • 1 — an error occurred. oop 😬

🍓 FILES 🍓

  • p.file — permissions (lock) file for checked-out versions. See sccs-get(1) for a description of the layout of the p.file. 🔒
  • s.file — SCCS history file, see sccsfile(5). 📜
  • dump.core — if the file dump.core exists in the current directory and a fatal signal is received, a coredump is initiated via abort(3). yeah that's real, spicy but real 🔥

🦄 ATTRIBUTES 🦄

See attributes(7) for descriptions of the following attributes:

  • Availability → SUNWsprot
  • Interface Stability → Standard

💖 SEE ALSO 💖

sccs(1), sccs-add(1), sccs-admin(1), sccs-branch(1), sccs-cdc(1), sccs-check(1), sccs-clean(1), sccs-comb(1), sccs-commit(1), sccs-create(1), sccs-cvt(1), sccs-deledit(1), sccs-delget(1), sccs-delta(1), sccs-diffs(1), sccs-edit(1), sccs-editor(1), sccs-enter(1), sccs-fix(1), sccs-get(1), sccs-help(1), sccs-histfile(1), sccs-info(1), sccs-init(1), sccs-istext(1), sccs-ldiffs(1), sccs-log(1), sccs-print(1), sccs-prs(1), sccs-prt(1), sccs-rcs2sccs(1), sccs-remove(1), sccs-rename(1), sccs-rmdel(1), sccs-root(1), sccs-sccsdiff(1), sccs-status(1), sccs-tell(1), sccs-unedit(1), sccs-unget(1), sccs-val(1), bdiff(1), diff(1), what(1), sccschangeset(5), sccsfile(5), attributes(7), environ(7), standards(7).

like, the whole friend group showed up 🫂

🩷 DIAGNOSTICS 🩷

Use the SCCS help command for explanations (see sccs-help(1)). when in doubt, ask help 💬

🙈 BUGS 🙈

None currently known. periodt 💅✨

Mail bugs and suggestions to schilytools@mlists.in-berlin.de or open a ticket at https://codeberg.org/schilytools/schilytools/issues. we love a bug report that comes with suggestions 🫶

The mailing list archive may be found at:

https://mlists.in-berlin.de/mailman/listinfo/schilytools-mlists.in-berlin.de.

👑 AUTHORS 👑

The SCCS suite was originally written by Marc J. Rochkind at Bell Labs in 1972. Release 4.0 of SCCS — which introduced 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 glow-up was real 😭📈

The SCCS suite was later maintained by various people at AT&T and Sun Microsystems. Since 2006, the SCCS suite has been maintained by Joerg Schilling and the schilytools project authors. legends, honestly 👏

🌈 SOURCE DOWNLOAD 🌈

The source code for sccs is included in the schilytools project and may be retrieved from the schilytools project at Codeberg at

https://codeberg.org/schilytools/schilytools.

The download directory is

https://codeberg.org/schilytools/schilytools/releases.

okay that's the whole page, go forth and check out some files bestie 🦋💜 — this icon of a manpage dropped on SunOS 5.11, dated 2022/10/06, and it ate, no crumbs 💅🎀✨

📦 where this page comes from