Re: [PATCH] pagealign_alloc: don't loop endlessly

I've attached a revised version of my earlier patch that preserves more information and avoids problems when the exit handlers call error() after error() calls exit(). Regards, Derek Index: src/ChangeLog === RCS file: /cvs/ccvs/src/C

Re: MacOS X 10.3.7 Build Problem After CVS CheckOut

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Conrad T. Pino <[EMAIL PROTECTED]> writes: > I'm seeing the same build problem on both stable & feature: > > Titanium:~/projects/cvs-1.12.12 conradtpino$ make > make all-recursive > Making all in lib > make all-am > make[3]: Nothing to be done for

Re: [PATCH] pagealign_alloc: don't loop endlessly

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thorsten Glaser wrote: >Derek Price dixit: > >>Does the attached, more general, patch do the trick for you? > > >It does, but I do not get a diagnostic, neither on stderr >(CVS output) nor in syslog on server or client. This is >probably because the C

Re: [PATCH] pagealign_alloc: don't loop endlessly

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thorsten Glaser wrote: >Derek Price dixit: > >>>Yes, that's why I was suggesting to print the error message to stderr >>>so at least the client gets an idea about what happened and can slap >>>the server administrator. CVS does this for quite some occ

Re: [PATCH] pagealign_alloc: don't loop endlessly

Does the attached, more general, patch do the trick for you? I think the problem is deeper - error() really needs a way to bypass the memory allocation of the buffer routines, but this should work around the problem for now. Cheers, Derek Thorsten Glaser wrote: >Hello! > >Please apply the fol

Re: [PATCH] pagealign_alloc: don't loop endlessly

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thorsten Glaser wrote: >Derek Price dixit: > >>My patch logs the actual error message to the syslog too (via the >>vsyslog() call), but if your chroot is preventing access to the syslog, >>that wouldn't help anyhow. > > >Yes, that's why I was suggesti

Re: [PATCH] pagealign_alloc: don't loop endlessly

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thorsten Glaser wrote: >Derek Price dixit: > >>Does the attached, more general, patch do the trick for you? > > >It does, but I do not get a diagnostic, neither on stderr >(CVS output) nor in syslog on server or client. This is >probably because the C

Re: MacOS X 10.3.7 Build Problem After CVS CheckOut

Conrad T. Pino wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Derek, From: Derek Price [mailto:[EMAIL PROTECTED] I never thought it was worth coming up with a more automated solution, but you're welcome to try. I would argue against changing the name of the executable though, and I'm

Re: MacOS X 10.3.7 Build Problem After CVS CheckOut

Incidentally, I thought this was documented somewhere other than the email list, but I don't see it. I've added a note to INSTALL on stable and INSTALL-CVSon feature. Cheers, Derek Derek Price wrote: This is a well-known problem. The workaround is to use a build directory. i.e.: cvs co c

RE: MacOS X 10.3.7 Build Problem After CVS CheckOut

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Derek, > From: Derek Price [mailto:[EMAIL PROTECTED] > > I never thought it was worth coming up with a more automated solution, > but you're welcome to try. I would argue against changing the name of > the executable though, and I'm not sure

Re: MacOS X 10.3.7 Build Problem After CVS CheckOut

This is a well-known problem. The workaround is to use a build directory. i.e.: cvs co ccvs cd ccvs mkdir build cd build ../configure make I never thought it was worth coming up with a more automated solution, but you're welcome to try. I would argue against changing the nam

Re: PAM session support documentation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Murphy wrote: > 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 ma