Arch Linux

svacko

Member

Registered: 2008-07-08

Posts: 9

rc.conf update problem

Hi all,
i suffer from one strange problem. My arch installation was running long time without problems, then i needed to add some modules and daemons to start and load during boot process and edited rc.conf. I made a mistake and added module's names (instead of daemon's names) into the daemons section what logically ended with error starting (unexisting) daemon during boot process. What more, important daemons (hal, network, alsa,...) which should be loaded after this incorrect modules weren't started at all. After i realized i made a mistake i've few times corrected rc.conf, but problem is, that arch is still not accepting these new changes and tries to still daemons, which are not in the daemons list in rc.conf.

Could somebody give me a clue, what to correct more or how to troubleshoot the problem?

Thanks in advance,
Stanley

nixpunk

Member

Registered: 2009-11-23

Posts: 271

Re: rc.conf update problem

Could you possibly be mixing up rc.conf and rc.conf.pacnew?  I would just check that to be sure for starters.

svacko

Member

Registered: 2008-07-08

Posts: 9

Re: rc.conf update problem

thanks for the reply. i'm periodically updating rc.conf so no, there is no new rc.conf.pacnew.

The problem brought problems with hal/dbus. After successful login through kdm, following error appears:
Cannot open ConsoleKit session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

and i need to manually start network, sound,... hal is not running. It's really strange

mcmillan

Member

Registered: 2006-04-06

Posts: 737

Re: rc.conf update problem

It probably would be helpful if you would post your rc.conf so we can see what it looks like rather than just your description of what you think it is.

svacko

Member

Registered: 2008-07-08

Posts: 9

Re: rc.conf update problem

#
# /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="localtime"
TIMEZONE="Europe/Bratislava"
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=(!pcspkr)
#MODULES=(!pcspkr powernow-k8 cpufreq_ondemand cpufreq_powersave cpufreq_userspace)

# 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="svacko"

# 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="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
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)
 
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# 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 dbus hal network !netfs @openntpd crond @sshd alsa)

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: rc.conf update problem

problem is, that arch is still not accepting these new changes and tries to still daemons, which are not in the daemons list in rc.conf

Rather impossible.
Do you heed both dbus and hal in DAEMONS? Hmmm, maybe you should capitalize that keyword - 'DAEMONS' instead of 'daemons'.

Edit: on my other box I have both hal and dbus so that shouldn't hurt, but lowercase 'daemons' seem not to work so this may be it.

Last edited by karol (2010-07-05 16:16:16)

svacko

Member

Registered: 2008-07-08

Posts: 9

Re: rc.conf update problem

i'm really sorry,
but starting daemons according to rc.conf is working OK I didn't check rc.local startup script, which was starting daemons, which were not in rc.conf and therefore i thought problem is in rc.conf. SO no problem, everything is working OK

Thanks for your time,
S.