Date: Thu, 21 Dec 2017 20:22:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224507] New port: devel/liblockfile standard lockfile library Message-ID: <bug-224507-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224507 Bug ID: 224507 Summary: New port: devel/liblockfile standard lockfile library Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: yasu@utahime.org Created attachment 189015 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D189015&action= =3Dedit patch file This library implements a number of functions found in -lmail on SysV syste= ms. These functions are designed to lock the standard mailboxes in /var/mail (or wherever the system puts them). In additions, this library adds a number of functions to create, manage and remove generic lockfiles. The lockfiles are created by this library in an NFS-safe manner, that is by using a tempfile and using link(2) to create the lockfile. It works around several defects in NFS servers to make sure the lockfile is created atomica= lly. The locking strategy is compatible with other well-written NFS-safe programs that create lockfiles - such as procmail, exim and mutt. If you are trying to lock a mailbox in a directory writable for group mail,= the locking functions will call a helper application which runs setgid to do the actual locking. The helper application "dotlockfile" can also be used direc= tly, for example for use in shellscripts. This means a program such as a MUA doesn't need to be setgid mail anymore t= o be able to lock the mailbox. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224507-13>