runlevel. Therefore, it appears that it is used to set the default
runlevel.
However, according to this forum exchange, it's ignored by upstart. I
stumbled
across this while googling for Fedora 9 runlevel 3:
http://fcp.surfsite.org/modules/newbb/viewtopic.php?viewmode=flattopic_id=54512forum
On Sun, 15 Jun 2008 19:25:05 -0400
Bob Barrett [EMAIL PROTECTED] wrote:
I have never before had this kind of problem. The kind where
the developers go off on some experimentation tangent, but
supply so little information for the users. I'm disappointed in
Fedora 9.
That's hard to believe: It
On Tue, Jun 3, 2008 at 8:32 PM, Tom Horsley [EMAIL PROTECTED] wrote:
On Tue, 03 Jun 2008 20:44:19 -0400
Bob Barrett [EMAIL PROTECTED] wrote:
I'd sure like to
know what other process is running while /bin/login is waiting for me to
login.
Maybe you could replace telinit with a script
Javier Perez wrote:
On Tue, Jun 3, 2008 at 8:32 PM, Tom Horsley [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
On Tue, 03 Jun 2008 20:44:19 -0400
Bob Barrett [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'd sure like to
know what other process is running while
g wrote:
Kevin J. Cummings wrote:
menu.lst is better known in the Fedora world as: /etc/grub.conf
if menu.lst is left as a link, which it does not seem to have to be.
I have employed the brute force solution:
/usr/sbin/gdm
[F8:[EMAIL PROTECTED] /etc/rc.d]# l /usr/sbin/gdm
On Tue, 03 Jun 2008 20:44:19 -0400
Bob Barrett [EMAIL PROTECTED] wrote:
I'd sure like to
know what other process is running while /bin/login is waiting for me to
login.
Maybe you could replace telinit with a script that does a ps to a log
file, then execs the original telinit?
I certainly
Kevin J. Cummings wrote:
g wrote:
Bob Barrett wrote:
It looks like it has booted in runlevel 3, but something is then
running telinit 5. I've searched recent mails to this list, and
I've searched the startup scripts, /etc/rc.d/rc3.d, etc., but have
not been able to find anything. Any
Thanks, guys, but it's not in /boot/grub/grub.conf. I'm sorry I didn't
list every file I've looked at, but I have looked at everything in
/etc/rc.d. I ran these commands:
But startup is now being done via upstart. You also need to poke around
in /etc/event.d for possible culprits :-).
--
