Date: Tue, 14 Jun 2005 23:37:48 -0400 From: Ed Maste <emaste@phaedrus.sandvine.ca> To: freebsd-current@freebsd.org, Maxim Konovalov <maxim@macomnet.ru> Subject: Re: savecore(8) increments /var/crash/bounds on each boot Message-ID: <20050615033748.GA84053@sandvine.com> In-Reply-To: <20050615023600.GA20721@dragon.NUXI.org> References: <20050613192308.GA87640@sandvine.com> <20050614082039.GA2038@dragon.NUXI.org> <20050614224704.Y75797@mp2.macomnet.net> <20050614190854.GA12928@dragon.NUXI.org> <20050614235132.L76669@mp2.macomnet.net> <20050615023600.GA20721@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 14, 2005 at 07:36:00PM -0700, David O'Brien wrote: > Do you understand the fix? How does lying in printheader() fix anything? > Moving the call to getbounds() back to the original location is the "fix" > but then it negates -vv. We shouldn't lie in printheader(). The problem is of course that getbounds() not only gets the count from the bounds file but also increments it. The decision to write a core hasn't been made at the time printheader is called for -vv. Thus the reported bounds might not correspond to a core. The newly added dump status is also meaningless in the -vv case, since the status may still be determined after the -vv printheader. How about just not showing the bounds for the -vv case? -- Ed Maste, Sandvine Incorporated
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050615033748.GA84053>