You are not logged in.
Pages: 1
I am just trying to get to grips with the init system of Arch (I am used to the sysv method).
I have seen the word "backgrounding" mentioned a few times, but cannot find a reference to what it actually does, so would be interested in a quick explanation.
Cheers, Nick
Offline
afaik backgrounding a daemon simply starts it during others start. It looks like the daemon gets skipped, but the daemon starts, the init just doesnt wait for it to finish.
Offline
Basically, with our init, daemons are specified in an array in rc.conf as such:
DAEMONS=(syslog-ng cups alsa)
To background one, you stick an @ just before the name:
DAEMONS=(syslog-ng @cups @alsa)
This will cause the daemon start script to run in the background (equivalent of running '/etc/rc.d/cups start &') and not wait to see if the daemon successfully started. Generally this is done with non-critical daemons, or daemons that aren't a dependency of another daemon, to speed up boot-time
Offline
Some daemons don't work for me if I do this - hal, fam, and cups among them. All complained of not being able to bind to a privileged socket (as if they weren't being run by root, which is mysterious to me). I put them back to foreground and forgot about it... I wonder if this is worth a bug report.
Offline
Offline
Actually, now that you mention it, ataraxia, I remember having that problem with cups too, and un-backgrounding it. Just for reference, here's my current array:
DAEMONS=(syslog-ng network dbus hal cups @spamd @sensors @clamav @netfs @crond @samba @alsa @ntpdate @archstatsrc)
Offline
I'm able to run cups fine in the background:
DAEMONS=(!syslog-ng @network @dbus @hal @crond @acpid @alsa !powersaved @cpufreq @hplip @cups kdm !dhcdbd !networkmanager)
We do not want a world in which the guarantee that we will not die of starvation is bought by accepting the risk of dying of boredom. -Raoul Vaneigem / Students for a Human Society
Offline
Pages: 1