summaryrefslogtreecommitdiff
path: root/pkgtools/shlock/files
AgeCommit message (Collapse)AuthorFilesLines
2008-05-30Don't set NOMAN for SunOS.tnn1-6/+1
2006-12-07Allow build on Linux.rpaulo1-2/+3
2005-05-25For DragonFly. This is from PR #30262 from Joerg Sonnenberger.reed1-2/+2
I didn't test under DraginFly myself.
2005-05-25Make this compile and install on Darwinrh1-2/+2
2002-02-15Set empty DISTFILES so no fetch is really attempted.seb1-1/+5
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.
2002-01-15Initial import of Erik E. Fair's shlock utility, with sources taken fromagc3-0/+471
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.