Adsl in rc.conf daemon array

I tried to start pppoe as a background daemon @adsl in rc.conf, but it just doesn't work. It works fine when manually pppoe-start or as a non-background daemon, but it takes time to dial up.
So how to configure it correctly?

loserMcloser wrote:Do you have a firewall starting up after adsl in rc.conf? If so, maybe some firewall setting is stopping the pppoe connection attempt?
No. I don't have a firewall.
And the log message is the same as manually connect, which connect pppoe correctly.
@adsl is the last daemon I start, but I'm not sure if there are some dependencies here.

Similar Messages

Rc.conf: A reasonable DAEMONS array when using sysvinit is?

My latest rc.conf.pacnew suggests that having a reasonable DAEMONS array when using sysvinit is a good thing to have.
Right now the only line left I am using in my rc.conf is:
DAEMONS=(syslog-ng net-profiles dbus crond ntpd)
But is it a reasonable Daemons array?

If you need a daemon after booting the system, add it to the array. If a daemon requires another daemon, put it after the dependency. If a daemon does neither depend on anything like other daemons or network, put it in the and and write @daemonname to start it in the background. My other rules of thumb used to be: start syslog early, start dbus early.

How do i add the "hal" daemon to the DAEMONS array in /etc/rc.conf?

I know how to get into the editor for /etc/rc.conf , but what exactly do i type to add "hal" to the array?

Gowireless - please, use some common sense when reading the documentation.
DAEMONS Section
This array simply lists the names of those scripts contained in /etc/rc.d/ which are to be started during the boot process, and the order in which they start. Asynchronous initialization by backgrounding is also supported and useful for speeding up boot.
DAEMONS=(network @syslog-ng netfs @crond)
I dunno, maybe putting in hal into the DAEMONS array would work?
Also, it's really annoying for you to create a new thread every two hours with a new question that could be solved by following the beginner's guide step by step. If you follow it carefully, your problems will all be solved. Trust me. When I first started using Arch, following the beginner's guide did wonders for my Arch Linux installation.

Default rc.conf daemons

Just curious what network netfs and crond do ? They are loaded at startup in the daemons array of the default rc.conf and i am trying to reduce my startup processes and trying to determine if i need them.
Thanks

carick wrote:Just curious what network netfs and crond do ? They are loaded at startup in the daemons array of the default rc.conf and i am trying to reduce my startup processes and trying to determine if i need them.
Thanks
if you're trying to cut down on boot up time, putting '@' in front of each daemon will load them in the background. when i did that, it took about 10 seconds off my boot up time.

Pimp my rc.conf daemons

From what I understand, selective editing of the DAEMONS line of rc.conf, including prefixing certain daemons with @, can significantly reduce boot time. I read a couple posts, as well as the wiki, searching for a solid answer, but the best I found was "which services to start background depends on your needs" which is a bit obvious. In any case, here's my current line:
DAEMONS=(syslog-ng !network netfs crond hal alsa hplip cups dhcdbd networkmanager laptop-mode gdm)
I'm sure it's a mess, as I've just slapped daemons on to fix problems, enable wireless, etc. so far.
If it's at all useful, this is a laptop that I commonly use as a workstation and with wireless.
Last edited by ArchPad (2007-06-13 14:34:41)

toofishes wrote:
ArchPad wrote:
From what I understand, selective editing of the DAEMONS line of rc.conf, including prefixing certain daemons with @, can significantly reduce boot time. I read a couple posts, as well as the wiki, searching for a solid answer, but the best I found was "which services to start background depends on your needs" which is a bit obvious. In any case, here's my current line:
DAEMONS=(syslog-ng !network netfs crond hal alsa hplip cups dhcdbd networkmanager laptop-mode gdm)
I'm sure it's a mess, as I've just slapped daemons on to fix problems, enable wireless, etc. so far.
If it's at all useful, this is a laptop that I commonly use as a workstation and with wireless.
Certain daemons likely depend on other things already having started before they initiate their startup, so you want to leave some alone. Here is my array, and although different than yours, notice how I leave quite a few things un-backgrounded due to dependencies and lump all the backgrounded ones at the end:
DAEMONS=(syslog-ng network iptables portmap @fcron @hal @sensors @knockd @netfs @sshd @ntpd @alsa @cups)
This would lead me to believe something like this would work for you (and WHY do you have network disabled?):
DAEMONS=(syslog-ng network hplip @crond @hal @netfs @alsa @cups @dhcdbd @networkmanager @laptop-mode @gdm)
I have syslog-ng and network backgrounded too and that works perfect.

Rc.conf deamons array - question

i have a question about the deamon array in rc.conf, this is mine:
DAEMONS=(preload syslog-ng dbus acpid netfs alsa crond hal acpi-support fam stbd wicd gpm cups samba asusoled-clockd bluetooth transmissiond sshd)
i know there is an order for some things, i just dont know what, so my question, is my order ok? if not what do i need to switch?
thanks

adamruss wrote:
Inxsible wrote:
adamruss wrote:
i have a question about the deamon array in rc.conf, this is mine:
DAEMONS=(preload syslog-ng dbus acpid netfs alsa crond hal acpi-support fam stbd wicd gpm cups samba asusoled-clockd bluetooth transmissiond sshd)
i know there is an order for some things, i just dont know what, so my question, is my order ok? if not what do i need to switch?
thanks
As long as the daemons are independent of each other, it hardly matters what order they are started in. The only thing is that the syslog-ng is used for logging...so you always want to start that before anything else so that in case there are errors in starting any daemon, they will logged and you can see them later.
I am not sure what 'preload' daemon is. Also you might want to start the unimportant ones in the background by prefixing them with an '@' sign so that your boot up would be quicker.
what do you mean unimportant?
You could bacground "alsa gpm cups samba bluetooth".
Oh, and if you don't use any network filesystems remove netfs. Don't have any cronjobs remove crond.

Rc.conf DAEMONS '@' question

In rc.conf it says to put a @ infront of a daemon to load it in the background.
What exactly does this mean and which daemons should I consider loading up in the background?
Cheers.

It means the next daemon listed will start without waiting for the prefixed daemon to finish.. uh, e.g my daemons line:
DAEMONS=(syslog-ng network dbus hal portmap @fam @shorewall @samba @netfs @crond @alsa @mpd)
Basically, shorewall will start before fam has finished loading, and so on. You have to use a little common sense to figure out what needs to be running before other things can - like portmap must be running before fam I believe. I'm not sure my setup is optimal, I could perhaps background one or two more, but i'm not all that concerned right now.
Anyway it's worth playing with and this setup saves me maybe 10-20 secs in boot time at a guess.

RC.CONF Daemon & Module Order?

Hello,
I haven't found much related to the topic from some searches I have conducted, but I have been wondering. Is there a prefered order to items within the Daemon and Module lines within rc.conf? If so, could someone please provide a link to the page/document? Thanks.

the default order is good to start with. The only thing you have to worry about is the fact that certain daemons require another to be started first. For example, dbus needs to load before hal and ivman needs to load after both. You really need to know and understand the daemon in order place it properly, but if you're using them already it shouldn't be hard.
The rest is personal preference.

Initscripts default rc.conf DAEMONS line and HAL

Hello,
Some application error messages recently caused me to realize that after setting up a new machine I was not starting the HAL daemon.
Shouldn't this daemon be in the default DAEMONS=() line of rc.conf, as installed by the initscripts package?
I started to flag the package "out of date" but I wasn't sure if this was the appropriate action for this issue/question.
android

I was refering to flaging the initscripts package, not the hal package.
It's my impression that udev hot plugging as well as kde and gnome infrastructure (therefore all of the applications, not just if that's your desktop) all rely on hal at runtime.
I still haven't quite run it to ground, but I also believe that the arch boot proccess uses hal as part of hardware discovery.
So I think quite a bit of stuff depends on it and that it's a default in arch installations.
Given this, it seemed it would be reasonable if it were included in the DAEMONS line by default, or at least if configuration dependent on it is selected at system installation time.
In short, it seems like initscripts is "out of date" by not supporting hal out of the box.
This issue is related to knowing which of the, ever growing list of, groups to which a user should be added in order to have access to the systems hardware. But that's another post.
This is just my impression as a user. I'm eager to learn more, especially about the arch setup and boot process.
Thanks for your reply...
johnea

[SOLVED] Daemons Array Question

Two questions, actually:
1) When I installed wicd, the Arch Wiki told me to disable the network daemon with "!network". What is the difference between using the exclamation mark and just removing the word "network" from the array?
2) From what I can tell, netfs is used to access files on a network, like a LAN, correct? If I don't use that functionality on my laptop, is there any reason to keep this daemon at all? (i.e. does it have any effect on my internet access?)
Last edited by dfetter88 (2010-06-15 03:32:50)

1) When I installed wicd, the Arch Wiki told me to disable the network daemon with "!network". What is the difference between using the exclamation mark and just removing the word "network" from the array?
Nothing really.
2) From what I can tell, netfs is used to access files on a network, like a LAN, correct? If I don't use that functionality on my laptop, is there any reason to keep this daemon at all? (i.e. does it have any effect on my internet access?)
That's right. It will mount the network locations from your /etc/fstab

[SOLVED] Start offlineimap as a daemon?

I just installed offlineimap so I can use mutt to view IMAP email. How can I start it as a daemon so it automatically syncs email upon login? I found an rtorrent daemon script on the forum and just changed it to offlineimap, but it has a few problems.
1. It does not work upon init. It works if I manually do /etc/rc.d/offlineimap start.
2. It does not stop at all, regardless of how I do it - either manually or automatically.
Anything I can do to get this working?
Thanks.
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
[ -z "$OFFLINEIMAP" ] && OFFLINEIMAP=/usr/bin/offlineimap
[ -z "$OFFLINEIMAP_USER" ] && OFFLINEIMAP_USER=oliver
[ -z "$OFFLINEIMAP_HOME" ] && OFFLINEIMAP_HOME=/home/oliver
[ -z "$OFFLINEIMAP_SOCKET" ] && OFFLINEIMAP_SOCKET=$OFFLINEIMAP_HOME/.socket
[ -z "$OFFLINEIMAP_LOCK" ] && OFFLINEIMAP_LOCK=$OFFLINEIMAP_HOME/.session/offlineimap.lock
[ -z "$OFFLINEIMAP_DTACH" ] && OFFLINEIMAP_DTACH="/usr/bin/dtach -n $OFFLINEIMAP_SOCKET -z"
case "$1" in
start)
stat_busy "Starting offlineimap"
PID=`pidof -o %PPID $OFFLINEIMAP`
if [ -z "$PID" ]; then
[ -S $OFFLINEIMAP_SOCKET ] && rm $OFFLINEIMAP_SOCKET &> /dev/null
[ -f $OFFLINEIMAP_LOCK ] && rm $OFFLINEIMAP_LOCK &> /dev/null
fi
/bin/su -c "$OFFLINEIMAP_DTACH $OFFLINEIMAP &> /dev/null" \
$OFFLINEIMAP_USER
if [ $? -gt 0 ]; then
stat_fail
else
add_daemon offlineimap
stat_done
fi
stop)
stat_busy "Stopping offlineimap"
PID=`pidof -o %PPID $OFFLINEIMAP`
[ ! -z "$PID" ] && kill -s INT $PID &> /dev/null
if [ $? -gt 0 ]; then
stat_fail
else
rm_daemon offlineimap
stat_done
fi
restart)
$0 stop
sleep 1
$0 start
echo "usage: $0 {start|stop|restart}"
esac
exit 0
Last edited by MTsoul (2009-02-04 08:10:21)

MTsoul wrote:1. It does not work upon init. It works if I manually do /etc/rc.d/offlineimap start.
Have to ask, as you didn't mention it - did you add it to the rc.conf DAEMONS array?

Netcfg configuring a pppoe

buddys :}
I was reading the wiki netcfg and still could not solve my doubts. Well, the point is that I use a modem in BRIDGE mode and at home I connect the Internet with a username and password from the ISP:)
I saw there in the "/ etc / network.d / examples" a file named ppp:
CONNECTION='ppp'
INTERFACE='eth0'
PEER='provider'
PPP_TIMEOUT=10
but I think to access with username and password I have a few more lines to add them, just do not know what the tags to set this type of information within the profile

i havent used pppoe with netcfg before, but you can pppoe by installing the rp-pppoe package and editing /etc/ppp/pppoe.conf and then starting /etc/rc.d/adsl
you can then change the ppp profile to start the adsl script or simply add it to the rc,conf daemon array.

[SOLVED] Authentication failure while try to login in GDM

Hi,
I just installed Arch Linux 64 bit on Virtualbox (I using GNOME and GDM). I have set on rc.conf daemon arrays to start dbus and gdm and it run well.
My problem is I can't login using root. When I try to login, it prompt Authentication failure
I can't re-configure my rc.conf because I can't login, and I stuck in GDM screen..
When I try to use "Ctrl+Alt+F1", it effects to my host (ubuntu), not to my guest Arch
How to skip GDM to started for this condition and how to solve this authentication failure ?
Last edited by alphazero (2011-11-20 11:51:19)

Since I run on virtualbox. I can't use Ctrl-F1, so I try to edit rc.conf using LiveCD
After I modify rc.conf and remove gdm in daemon array, I reboot and login as root.. adduser and finally it works login as user
And I add again gdm after it worked to log as user.
So problem solved.. Thanks to wonder for your help.
Last edited by alphazero (2011-11-20 11:50:54)

[Solved] intel-ucode/amd-ucode

EDIT: Solution is in Post #4
I have a question about: intel-ucode. It says it's a microcode update for intel processors (there is a corresponding AMD package but I'm intel). I already have "microcode_ctl" installed and for some reason that package will just not show up in the Packages search on this site. Has it been depreciated in favor of "intel-ucode"? Should I have both installed? Should I remove "microcode_ctl" and install "intel-ucode"?
$ pacman -Ss microcode_ctl
extra/microcode_ctl 1.17.20111110-1 [installed]
A companion to the IA32 microcode kernel driver
(This is my local output as an installed package but the package search function of this forum returns no hits)
Edit: Also, I have "microcode" in my rc.conf daemons array as it's supposed to be so if I uninstalled it and added intel-ucode would I have to do something similar? It's frustrating when you don't find any obvious documentation for a package..
Last edited by headkase (2012-01-10 01:00:24)

josephk wrote:please, update the microcode page in wiki
I would edit the wiki but I just don't know if the instructions are the same for "amd-ucode." I'm an intel owner only and have only done it once on my own machine. The wiki should be updated but, for myself, I don't have all the facts to do so.
If someone else would like to take a shot at it, here is the wiki page in question:
https://wiki.archlinux.org/index.php/Microcode
The references to "microcode_ctl" are now non-existent. That package is now gone as anyone can now verify themselves.
Edit: there is a reference on the page now which talks about "using testing" with the intel-ucode and amd-ucode packages. That now needs to be the primary information and the microcode_ctl information needs to be stripped out.
Last edited by headkase (2012-01-11 02:03:54)

[SOLVED] Borked my Arch! Hanging at boot...

Hi, I've been using Arch on my netbook for the last couple of months with great results until just now....
Yesterday everything was going great guns, then I booted a different distro (remixOS) from a persistant usb install. After a few hours I rebooted Arch but it hung shortly after entering init runlevel 3, whilst trying to start the laptop-mode daemon. I read about a laptop-mode related bug that prevented users from booting and, believing that laptop-mode was the culprit, booted into a Linux Mint live session and edited my rc.conf daemons array.
However this has not solved the problem, my machine now just hangs at "Starting crond daemon" with a [BUSY] message on the right hand side of the screen and the cursor frozen.
What should I do? I use this machine for school and I don't want to reinstall, I'd prefer to learn about the issue and fix the problem myself.
Sorry if this is the wrong place for this thread, I've searched extensively but haven't found anything that matches my problem and other threads about chrooting and init runlevels are too loaded with jargon for me to comprehend at this point.
Thanks for reading about my problems.
Toby.
Last edited by TobyJamesJoy (2012-07-28 04:16:39)

TobyJamesJoy wrote:
Haha, mkinitpcio -p linux worked! Posting from Arch! Thanks so much Zancarius!
I have tried to pacman -Syu but i have a dependancy cycle with lib32-gcc-libs and gcc-libs-multilib but that's most likely covered in another thread.
Well, my mind's a bit boggled. Sounds like it might've been from an update or simple oversight. I've had issues with mkinitcpio not generating the correct initrd--once from my own mistake (not updating mkinitcpio.conf correctly) and once from it running but apparently not including LVM even though I instructed it to. (I suspect the latter might've also been from an oversight on my part.)
Here's a thread that might help with the lib32-gcc-libs/gcc-libs-multilib issue.
TobyJamesJoy wrote:I did get some colourful error messages in my boot too so here's my /etc/fstab:
Assuming your UUIDs are correct, your fstab looks fine. The only change that you might need is to set the pass field (last number) for /boot and /home to 2 (see fstab(5)), but that wouldn't cause your problems.
Unless the kernel is screaming at you, you may occasionally see some things on boot that happen to be harmless. No biggy. :)
TobyJamesJoy wrote:
And a link to my /boot/grub/menu.lst which was indeed installed from arch.
I know that there is a quiet flag in my kernel options because I noticed it when I was experimenting with switching the runlevels via grub but I'm not certain where to find my kernel line, nor what constitutes "unsusual options". I'm pretty sure I didn't change anything for ACPI support but maybe some laptop-mode-tools stuff did someting, I can't be sure...
The boot looks fine, especially since mkinitcpio fixed your problem. "Unusual options" in this case would be things like turning off various kernel features or passing in options to change behavior--you'd know them if you saw them. You don't have them, so it's nothing to worry about.
Good to know that solved your problem. Don't forget to mark your thread [solved] too!
Edit: Whoops! I think you caught the [solved] before I did. Sorry! :)
Last edited by Zancarius (2012-07-28 04:37:16)

Adsl in rc.conf daemon array

Similar Messages

Maybe you are looking for