[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2011Q4 2008-05-30T10:02:38Z 2008-05-30T10:02:38Z tnn tnn 2008-05-30T10:02:38Z urn:sha1:6c6189e5d8b6eb49ce30d4d2076e8044c3984ffb 2006-12-07T19:10:21Z rpaulo rpaulo 2006-12-07T19:10:21Z urn:sha1:ebeb030f844a444a3e56d57a28f359987f09256d 2005-05-25T02:23:15Z reed reed 2005-05-25T02:23:15Z urn:sha1:4717e4067f310999b22c722d23aad6d8c82fe517 I didn't test under DraginFly myself. 2005-05-25T01:40:05Z rh rh 2005-05-25T01:40:05Z urn:sha1:544b27109df1cff0ecf3dc836dbe0c024568dbaf 2002-02-15T11:56:18Z seb seb 2002-02-15T11:56:18Z urn:sha1:691ca55fcfdaf7ef0121c9081bb9148a333d5a01 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-15T13:20:27Z agc agc 2002-01-15T13:20:27Z urn:sha1:14b8d476437bb7b45c23c19bb88f5cd7e61dd664 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.