Date: Tue, 10 Apr 2012 23:05:52 +0900 From: Taku YAMAMOTO <taku@tackymt.homeip.net> To: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de> Cc: Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: Changes to sbin/init/init.c (r233944) makes x11/xdm impossible to start from /etc/ttys Message-ID: <20120410230552.32898234.taku@tackymt.homeip.net> In-Reply-To: <4F83FF50.1010404@mail.zedat.fu-berlin.de> References: <4F83FF50.1010404@mail.zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks a lot to investigate this problem so deeply.
I have, maybe related, a bit strange phenomenon among xdm, too.
I have a bit different setup than others: I'm using modified
x11/gdm/files/gdm.in to launch xdm.
The problem is, when I start xdm manually from ttyvX like this:
exec sudo service xdm start
xdm won't start, while doing like this:
sudo service xdm start; sleep 10; exit
xdm starts happily.
To emulate this symptom for those who don't use rc.d/xdm, in ttyvX:
exec sudo sh -c "(sleep 10; /usr/local/bin/xdm) &"
(The amount to sleep may differ if some race conditions are involved.)
I guess the root cause seems to reside in accessing revoke(2)-ed
(or possibly, about to be revoke(2)-ed) tty.
I hope my shallow observation can shed some lights from different perspective.
--
-|-__ YAMAMOTO, Taku
| __ < <taku@tackymt.homeip.net>
- A chicken is an egg's way of producing more eggs. -
Post Scriptum:
In my environment and/or setup, xdm auto-starts fine 100% times
via rc.d on system startup.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120410230552.32898234.taku>