Date: Sun, 16 Jun 2013 11:24:00 -0600 From: Ian Lepore <ian@FreeBSD.org> To: Jeremy Chadwick <jdc@koitsu.org> Cc: Michiel Boland <boland37@xs4all.nl>, Konstantin Belousov <kostikbel@gmail.com>, FreeBSD Stable <freebsd-stable@FreeBSD.org> Subject: Re: system sporadically hangs on shutdown after switching to WITH_NEW_XORG Message-ID: <1371403440.4485.22.camel@revolution.hippie.lan> In-Reply-To: <20130616160752.GA26518@icarus.home.lan> References: <51BDD593.5000102@xs4all.nl> <20130616153710.GT91021@kib.kiev.ua> <51BDDE64.2040801@xs4all.nl> <20130616155502.GA26171@icarus.home.lan> <51BDE16D.3080903@xs4all.nl> <20130616160752.GA26518@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2013-06-16 at 09:07 -0700, Jeremy Chadwick wrote:
> On Sun, Jun 16, 2013 at 06:01:49PM +0200, Michiel Boland wrote:
> > On 06/16/2013 17:55, Jeremy Chadwick wrote:
> > [...]
> >
> > >Are you running moused(8)? Actually, I can see quite clearly that you
> > >are in your core.txt:
> > >
> > >Starting ums0 moused.
> > >
> > >Try turning that off. Don't ask me how, because devd(8) / devd.conf(5)
> > >might be involved.
> > >
> >
> > The moused is started by devd - I don't see a quick way of turning that off.
>
> Comment out the relevant crap in devd.conf(5). Search for "ums"
> and comment out the two "notify" sections.
I don't understand why people treat devd as if it's some sort of evil
virus that they're forced to live with (using phrases like "crap in
devd.conf"). In general, the standard devd rules tend to fall into 3
categories:
* use logger(1) to record some anomaly
* kldload a module
* invoke a standard /etc/rc.d script
For moused, the devd rules invoke /etc/rc.d/moused, which implies that
setting moused_enable=NO in rc.conf would be all that's needed to
disable it.
-- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1371403440.4485.22.camel>