locksoi, unlocksoi, rmdirsoi \- lock, unlock, and unlink soi directories.SH SYNOPSIS
.B locksoi
pathname...
.PP
.B unlocksoi
pathname...
.SH DESCRIPTION
.NXR "locksoi"
.NXR "unlocksoi"
.NXR "rmdirsoi"
.PN locksoi
changes the owner and group of the named directories changed to SOIand sets the mode set to 555 so that the directories' contents arefrozen. It clears any flags that may have been set by \fIunlocksoi.\f.PP
.I unlocksoi
changes the owner and group of the named directories changed to SOIand sets the mode set to 575. It also raises a lock flag preventinganyone else from unlocking the directories. Unlocked directories canhave their contents changed or removed.
.PP
.I rmdirsoi
is needed to completely remove a controlled directory without setting apermanent lock.
.PP
All of these commands work if and only if the caller is a member of group SOI.
.SH FILES
.TP 25
/etc/passwd, /etc/group
ID of pseudo-user \fIsoi\fR and group \fISOI\fR
.TP
~soi/lock
Lock files
.SH SEE ALSO
unlocksoi(1), clrgroup(1), soigroup(1)
.SH BUGS
These commands run \fIsuid\fR, and give anyone in group SOI access to any
directory, possibly denying write-access to the owner. Only members of group SOI can run them.
They also work for files, but makes them executable unconditionally.
They work but report incorrect error messages when used over a mount.
.I rmdirsoi
has no provision for recursively removing files. It should not be necessary. .SH AUTHOR
Chris Johnson
.rs
.SH HISTORY
1993-09-21
.br
1994-02-08
.br
SOI Version 0.8
.#$Id: locksoi.1,v 1.1 1994/02/17 00:10:10 CM Exp $ .#$Source: /home/soi/CM/man/man1/RCS/locksoi.1,v $ .#$Author: CM $