starting an rc.d throws me to the console

grooveharder · 2009-02-06 23:25:59

hey everyone,

greetings, nice to meet you all - i'm new to arch, but not to linux. i have a curious problem: every time (well, most times at least) an rc.d script is started after bootup, when i'm in X, the console (vt1 i think) is shown. thinking about it, could it be something to do with my splash configuration (and the CONSOLE=/dev/tty1 parameter)?

thanks for your help! arch is treating me very well so far

SamC · 2009-02-06 23:51:39

I'm sorry, but what is the problem here? Should you not be thrown to the console once the boot is finished?

grooveharder · 2009-02-07 00:12:55

sorry, maybe i wasn't very clear.

arch boots fine. beautifully, in fact. i just mean that when my system has fully booted and i'm already in X and start an rc.d script manually (such as cupsd when i plug my printer in), i am immediately thrown to vt1. is there any reason for this?

EDIT: i mean, when i start an rc.d script from an xterm, for example.

Last edited by grooveharder (2009-02-07 00:15:27)

SamC · 2009-02-07 00:19:37

Oh. Well, that works fine for me, here. Could you post the shortest one you can find that shows this behaviour?

quarkup · 2009-02-07 12:12:12

please could you post your /etc/rc.conf file ??

you can put the printer daemon to be started in startup, so you don't need to start manually the daemon

You should start (in the vc/1) the daemon manually so you could get the output.

Do this happens only for only one daemon or for any other daemon?

Last edited by quarkup (2009-02-07 12:17:43)

grooveharder · 2009-02-07 12:16:23

i know it can be started at startup, but i hardly use my printer, so i don't need cupsd running all the time.

here's /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"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# 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_GB.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/London"
KEYMAP="uk"
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=(!snd-hda-intel fuse lirc_mceusb2 !pcspkr vboxdrv vboxnetflt)

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

# 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
#
# eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
# INTERFACES=(lo !eth0)
# eth0="dhcp"

# 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=(NAS)


# -----------------------------------------------------------------------
# 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 @fbsplash !network @netfs @cpufreq @crond @oss @lircd @hal @fam @readahead-list-desktop net-profiles mpd mpdscribble gdm)

SPLASH="fbsplash"

quarkup · 2009-02-07 12:20:37

minor edit: it's probably the fbsplash daemon, as I'm using it now and experienced the same behavior.

Last edited by quarkup (2009-07-10 13:52:45)

konni · 2009-02-07 17:09:30

does this happen with any demon, even ones which loaded fine on boot? tried to restart alsa and got the same result?
or just cups? did you try without fbsplash as well?

Last edited by konni (2009-02-07 17:11:14)

Arch Linux

#1 2009-02-06 23:25:59

starting an rc.d throws me to the console

#2 2009-02-06 23:51:39

Re: starting an rc.d throws me to the console

#3 2009-02-07 00:12:55

Re: starting an rc.d throws me to the console

#4 2009-02-07 00:19:37

Re: starting an rc.d throws me to the console

#5 2009-02-07 12:12:12

Re: starting an rc.d throws me to the console

#6 2009-02-07 12:16:23

Re: starting an rc.d throws me to the console

#7 2009-02-07 12:20:37

Re: starting an rc.d throws me to the console

#8 2009-02-07 17:09:30

Re: starting an rc.d throws me to the console

Board footer