Re: [bug-gnulib] Re: [PATCH] mmap-anon.m4: use proper macro condition
On 2005/05/02, at 16:25, Mark D. Baushke wrote: Many thanks to Paul Eggert [EMAIL PROTECTED] who committed the patch to gl_FUNC_MMAP_ANON to check for message, not for MAP_ANON. I have updated the feature branch of CVS on cvshome.org to use the new version of the m4/mmap-anon.m4 file. Both confirmed. http://savannah.gnu.org/cgi-bin/viewcvs/gnulib/gnulib/m4/mmap- anon.m4.diff?r1=1.4r2=1.5 http://ccvs.cvshome.org/source/browse/ccvs/m4/mmap-anon.m4?r1=1.2r2=1.3 Thank you for all your effort regarding this problem. Regards, Moriyoshi ___ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs
Re: [bug-gnulib] Re: [PATCH] mmap-anon.m4: use proper macro condition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Many thanks to Paul Eggert [EMAIL PROTECTED] who committed the patch to gl_FUNC_MMAP_ANON to check for message, not for MAP_ANON. I have updated the feature branch of CVS on cvshome.org to use the new version of the m4/mmap-anon.m4 file. Enjoy! -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFCddX+3x41pRYZE/gRAv3bAJ9/5WqErJInzuM9Laa7cnzqvc64wgCgxP4g zK05B1vpndbZmDtttGdmbtc= =4fEN -END PGP SIGNATURE- ___ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs
PAM session support documentation
Hi Guys, I would like to commit the attached patch. It documents in the example files the necessary session lines in the PAM configuration file. I/we seem to have missed this when the session support was added. The manual has the necessary additions. OK with you? /Brian Index: contrib/pam/ChangeLog === RCS file: /cvs/ccvs/contrib/pam/ChangeLog,v retrieving revision 1.5 diff -r1.5 ChangeLog 0a1,4 2005-03-22 Brian Murphy [EMAIL PROTECTED] * cvs.linux, cvs.solaris: updated to add session support example. Index: contrib/pam/cvs.linux === RCS file: /cvs/ccvs/contrib/pam/cvs.linux,v retrieving revision 1.1 diff -r1.1 cvs.linux 8a9 session requiredpam_unix.so Index: contrib/pam/cvs.solaris === RCS file: /cvs/ccvs/contrib/pam/cvs.solaris,v retrieving revision 1.1 diff -r1.1 cvs.solaris 8a9 cvs session required/usr/lib/security/$ISA/pam_unix.so.1 ___ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs
Re: history and val-tags locks.
Derek Price wrote: HistoryFile=$CVSROOT/CVSROOT/logs/history/%Y%m%d So, if the history file path were configurable and run through strftime(), I can either (1) cache the history file name the first time it is determined and gaurantee that all the operations from the same server execution are logged to the same history file, or (2), re-strftime() each time history_write() is called, and guarantee that given two consecutive lines of any single history file, there was no CVS operation that occurred in the span of time between the lines. I'm leaning towards (1) since it is a little easier to code, only requires one set of system calls per CVS server run, and CVS always sorts history lines before displaying them anyhow. Anyone have any different opinions? Regards, Derek ___ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs
