Date: Fri, 21 Jun 2013 23:39:09 -0500 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Miguel Clara <miguelmclara@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Cannot startx on FreeBSD10 Current Message-ID: <20130622043909.GC74291@over-yonder.net> In-Reply-To: <loom.20130622T022435-478@post.gmane.org> References: <kpfa4f$9j6$1@ger.gmane.org> <51BB3D2A.3070509@gmail.com> <op.wyob10gn34t2sn@markf.office.supranet.net> <51BB40A5.9090409@gmail.com> <op.wyoc2d1e34t2sn@markf.office.supranet.net> <51BB4D49.6040603@gmail.com> <op.wyofa5f634t2sn@tech304.office.supranet.net> <loom.20130622T022435-478@post.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 22, 2013 at 12:29:49AM +0000 I heard the voice of Miguel Clara, and lo! it spake thus: > > The only way to turn off is but "force" and this can cause damage to > filesystems, this is indeed a very big issue, and I'm not sure if > its specific to KMS or some freebsd-current problem cause I have no > way to look into it! One little trick you might try is to login to a second VTY and run something like "sleep 60 ; shutdown -r now" before switching back and running startx; if it's just a UI crash/lockup rather than a whole-system such, that'll give you a clean reboot without FS damage. Of course, if it's a whole-system lockup, it won't, but that also means you can tell which it is, which may be diagnostically useful... (ssh'ing in from another machine is another way to track such things, but may be less convenient depending on your own setup...) -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130622043909.GC74291>