Daemons auto Backgroud?

Dethredic · 2010-02-16 13:35:22

So, when I boot up and it get to the daemons, they all go instantly. I don't even get to read their names.

I do auto log myself in, and most of the time hal and network aren't done yet (I can't move my mouse and pidgin can't connect).

Here is my /etc/rc..conf

[phil@fml ~]$ cat /etc/rc.conf
#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="America/Toronto"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(!net-pf-10 !snd_hda_intel !pcspkr !snd-pcsp)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="fml"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng hal netowrk )
[phil@fml ~]$

sHyLoCk · 2010-02-16 13:46:49

network typo

Press scroll lock to pause the screen.

Dethredic · 2010-02-16 14:28:11

dammit my dyslexia is bad. That shouldn't effect hal though would it?

sHyLoCk · 2010-02-16 14:32:12

No it shouldn't. Is hal failing? What does this say:

 # /etc/rc.d/hal restart

Last edited by sHyLoCk (2010-02-16 14:32:31)

Dethredic · 2010-02-16 22:16:31

sHyLoCk wrote:

No it shouldn't. Is hal failing? What does this say:
 # /etc/rc.d/hal restart

No errors. It also starts in like 1 second.

toad · 2010-02-16 22:29:44

So you are complaining that your box boots too quickly

You could always put a delay into /etc/rc.local or some such so that X only comes up once hal is done...

Dethredic · 2010-02-17 04:48:59

I'm just complaining that hal doesn't finish when it says its finished

Dethredic · 2010-02-17 22:13:48

even fixing the typo in the network didn't help. Although now it starts, no time is spent starting in the daemons line.

grey · 2010-02-18 09:02:44

Dethredic wrote:

I'm just complaining that hal doesn't finish when it says its finished

How do you know that it doesn't finish? 0.5 seconds is about normal for /etc/rc.d/hal start.

Dethredic · 2010-02-18 13:11:41

grey wrote:

Dethredic wrote:
I'm just complaining that hal doesn't finish when it says its finished
How do you know that it doesn't finish? 0.5 seconds is about normal for /etc/rc.d/hal start.

Although it does take only that much time when I do /etc/rc.d/hal restart, what other explanation could there be for not being able to use my mouse / keyboard for several seconds after openbox starts.

My other reason is the the network still doesn't start, it auto backgrounds even after spelling its name right.

elliott · 2010-02-18 13:47:27

Dethredic wrote:

Although it does take only that much time when I do /etc/rc.d/hal restart, what other explanation could there be for not being able to use my mouse / keyboard for several seconds after openbox starts.

If hal wasn't starting, X would just hang and you would be forced to restart. You would get a black screen with a cursor in the middle and nothing else. At least that is what happened to me the last time I did an install and had a brainfart.

Last edited by elliott (2010-02-18 13:48:19)

grey · 2010-02-18 16:07:13

Dethredic wrote:

... what other explanation could there be ... ?

Lot's, probably. Just because I can only think of one doesn't mean that is the one it has to be.

Dethredic · 2010-02-18 16:41:48

grey wrote:

Dethredic wrote:
... what other explanation could there be ... ?
Lot's, probably. Just because I can only think of one doesn't mean that is the one it has to be.

I just remember during my first install I didn't start hal before starting X, and I couldn't use my mouse / keyboard.

ArchSoarer · 2010-02-18 18:01:33

Check your /etc/inittab, if you have one line uncommented and with the "respawn" option... maybe is that you're starting daemons simultaneously. If that's the case, you should change "respawn" for "once".

Dethredic · 2010-02-18 18:25:23

ArchSoarer wrote:

Check your /etc/inittab, if you have one line uncommented and with the "respawn" option... maybe is that you're starting daemons simultaneously. If that's the case, you should change "respawn" for "once".

I have this:

id:5:initdefault:

x:5:once:/bin/su phil -l -c "/bin/bash --login -c /usr/bin/startx >/dev/null 2>&1"

ArchSoarer · 2010-02-18 21:32:01

Try using this instead:

id:5:initdefault:

x:5:respawn:/bin/su phil -l -c "/bin/bash --login -c /usr/bin/startx >/dev/null 2>&1"

Pretty sure that'll work...

Last edited by ArchSoarer (2010-02-18 22:03:35)

Dethredic · 2010-02-19 12:20:51

ArchSoarer wrote:

Try using this instead:
id:5:initdefault:

x:5:respawn:/bin/su phil -l -c "/bin/bash --login -c /usr/bin/startx >/dev/null 2>&1"
Pretty sure that'll work...

didn't work.

ArchSoarer · 2010-02-19 17:01:26

Dethredic wrote:

didn't work.

Damn. Have you tried to boot to GDM first?

Dethredic · 2010-02-19 17:47:06

ArchSoarer wrote:

Dethredic wrote:
didn't work.
Damn. Have you tried to boot to GDM first?

I haven't installed GDM. I guess I could install SLIM to test.

Dethredic · 2010-02-22 12:32:39

Sorry for the late response, but no luck.

kapz · 2010-02-22 14:03:22

Well dunno if I can relate this with your network problem but network halted(and KDE due to it) on my system, the issue was resolved by correcting the /etc/hosts config file. You may want to check that you mentioned the localhost name in that file(as shown in archwiki).

Dethredic · 2010-02-23 12:26:41

kapz wrote:

Well dunno if I can relate this with your network problem but network halted(and KDE due to it) on my system, the issue was resolved by correcting the /etc/hosts config file. You may want to check that you mentioned the localhost name in that file(as shown in archwiki).

everything looks good there.

algorythm · 2010-02-23 12:47:12

Are you really sure this is hal related? When you do /etc/rc.d/hal stop, you can't use your keyboard and mouse?

Dethredic · 2010-02-24 03:12:38

algorythm wrote:

Are you really sure this is hal related? When you do /etc/rc.d/hal stop, you can't use your keyboard and mouse?

ur right, I can move my mouse / use my keyboard. I really have no idea at this point.

kapz · 2010-02-24 10:17:06

Have you installed evdev pkg? You can give this a go:

http://wiki.archlinux.org/index.php/Evdev

Arch Linux

#1 2010-02-16 13:35:22

Daemons auto Backgroud?

#2 2010-02-16 13:46:49

Re: Daemons auto Backgroud?

#3 2010-02-16 14:28:11

Re: Daemons auto Backgroud?

#4 2010-02-16 14:32:12

Re: Daemons auto Backgroud?

#5 2010-02-16 22:16:31

Re: Daemons auto Backgroud?

#6 2010-02-16 22:29:44

Re: Daemons auto Backgroud?

#7 2010-02-17 04:48:59

Re: Daemons auto Backgroud?

#8 2010-02-17 22:13:48

Re: Daemons auto Backgroud?

#9 2010-02-18 09:02:44

Re: Daemons auto Backgroud?

#10 2010-02-18 13:11:41

Re: Daemons auto Backgroud?

#11 2010-02-18 13:47:27

Re: Daemons auto Backgroud?

#12 2010-02-18 16:07:13

Re: Daemons auto Backgroud?

#13 2010-02-18 16:41:48

Re: Daemons auto Backgroud?

#14 2010-02-18 18:01:33

Re: Daemons auto Backgroud?

#15 2010-02-18 18:25:23

Re: Daemons auto Backgroud?

#16 2010-02-18 21:32:01

Re: Daemons auto Backgroud?

#17 2010-02-19 12:20:51

Re: Daemons auto Backgroud?

#18 2010-02-19 17:01:26

Re: Daemons auto Backgroud?

#19 2010-02-19 17:47:06

Re: Daemons auto Backgroud?

#20 2010-02-22 12:32:39

Re: Daemons auto Backgroud?

#21 2010-02-22 14:03:22

Re: Daemons auto Backgroud?

#22 2010-02-23 12:26:41

Re: Daemons auto Backgroud?

#23 2010-02-23 12:47:12

Re: Daemons auto Backgroud?

#24 2010-02-24 03:12:38

Re: Daemons auto Backgroud?

#25 2010-02-24 10:17:06

Re: Daemons auto Backgroud?

Board footer