developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
Unconditionally set PKGSRC_LOCKTYPE to `none' to avoid bootstrapping problem.
Do not generate formatted manual and do not install source manual on Solaris or
else we would need to make this package depends on textproc/groff. IMHO this
should be avoided for this package as it can be considered a prerequisite for
building further packages.
NetBSD-current, into the NetBSD Packages Collection.
The shlock command can create or verify a lock file on behalf of a
shell or other script program. When it attempts to create a lock
file, if one already exists, shlock verifies that it is or is not
valid. If valid, shlock will exit with a non-zero exit code. If
invalid, shlock will re- move the lock file, and create a new one.
shlock uses the rename(2) system call to make the final target lock
file, which is an atomic operation (i.e. "dot locking", so named for
this mech- anism's original use for locking system mailboxes). It
puts the process ID ("PID") from the command line into the requested
lock file.
shlock verifies that an extant lock file is still valid by using
kill(2) with a zero signal to check for the existence of the process
that holds the lock.
This package is only for Solaris and Linux platforms at present.
