Date: Tue, 21 Jan 2014 12:23:12 +0000 From: "Montgomery-Smith, Stephen" <stephen@missouri.edu> To: "ctm-users@freebsd.org" <ctm-users@freebsd.org> Subject: Re: ports/devel/py-dogpile.core issue Message-ID: <52DE66AC.8030000@missouri.edu> In-Reply-To: <201401210725.s0L7PZVJ060732@sep.oldach.net> References: <201401210725.s0L7PZVJ060732@sep.oldach.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/21/2014 01:25 AM, Helge Oldach wrote: > Hi, >=20 > I was wondering why creating the port index file with >=20 > make -C /usr/ports index >=20 > failed on my box, pointing to some unresolved dependency with > devel/py-dogpile.core. As it seems, this port's files have never been > distributed through CTM. I can't find them in any of the xEmpty files, > nor in one of the deltas, though I guess they should have appeared in > delta ports-cur.10100.gz. >=20 > Thinking about it, I suspect this is a "feature" that goes wrong: While > it's clearly desireable not to include core dumps in the CTM deltas, > devel/py-dogpile.core is not a core dump file but a directory. >=20 > Can somebody please fix this? Thanks. The CTM creation process assumes that any file ending with .core is probably the result of a program (like cvsup or svn) crashing. That is why that file is not being copied across. I'll try to fix it today, or soon afterwards. It would help if someone could remind me of how to tell the OS to stop dumping core when programs crash. I know it is a setting with "limits" or "limit", or perhaps some setting in /etc/login.conf would fix it. But whenever I have done this in the past, it has taken me a little while to get the settings just right. And if I send dumped core through CTM, it will make huge deltas.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52DE66AC.8030000>