Date: Thu, 18 Oct 2001 12:49:47 -0700 From: "Crist J. Clark" <cristjc@earthlink.net> To: freebsd-questions@FreeBSD.ORG Subject: Re: Security check output questions Message-ID: <20011018124947.C300@blossom.cjclark.org> In-Reply-To: <20011017121153.A2196@acadia.ne.mediaone.net>; from leblanc%2Bfreebsd@acadia.ne.mediaone.net on Wed, Oct 17, 2001 at 12:11:54PM -0400 References: <20011017121153.A2196@acadia.ne.mediaone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 17, 2001 at 12:11:54PM -0400, Louis LeBlanc wrote:
[snip]
> > Oct 16 13:56:25 leblanc /kernel: pid 86613 (cheetah), uid 118: exited on signal 11 (core dumped)
[snip]
> Now, the first is just one of many I get from the multitude of
> xscreensaver dumps. I am always having to clean up the *.core files
> from the various screensaver programs that just dump for whatever
> reason. Anyone know of a way to *prevent* these dumps? Other than
> the obvious "don't run xscreensaver" or "don't run the random
> screensavers". The random screensavers is my FAVORITE part of the
> xscreensaver. Failing any real solution, I'll probably just continue
> to clean out the cores. Maybe even search the ports archives for any
> references.
You can specify from which screensavers xscreensaver(1) should
"randomly" choose. Make a list of ones that do not crash. You can put
them in your resources file for example,
xscreensaver.timeout: 5
xscreensaver.cycle: 5
xscreensaver.splash: off
xscreensaver.programs: \
bubbles -root -nodelay -broken \n\
bubbles -root -nodelay -simple \n\
compass -root \n\
coral -root \n\
.
.
.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011018124947.C300>