Arch Linux

dudko

Member

Registered: 2010-03-04

Posts: 41

Login prompt mixed up with daemons

Hi,
I'm getting login prompt mixed up with daemons. Here is the sreenshot.

[dudko@archy ~]$ grep -i daemons= /etc/rc.conf
DAEMONS=(wicd)

Could you help me, please?
Thanks.:)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,354

Re: Login prompt mixed up with daemons

Are you using systemd or the are you using the default initscripts?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

HeSaid

Member

From: southwest Florida USA

Registered: 2010-07-02

Posts: 53

Re: Login prompt mixed up with daemons

You need dbus in your daemons before wicd.

DAEMONS=(dbus wicd)

You will probably need other daemons to make other things work, for example cupsd for printing.
Here is my daemon list:

DAEMONS=(syslog-ng dbus wicd @acpid @laptop-mode @cupsd @cpufreq @ntpd @crond)

--
Neal

---

Registered Linux User 159445.

dudko

Member

Registered: 2010-03-04

Posts: 41

Re: Login prompt mixed up with daemons

Are you using systemd or the are you using the default initscripts?

default.

You need dbus in your daemons before wicd.

DAEMONS=(dbus wicd)

You will probably need other daemons to make other things work, for example cupsd for printing.
Here is my daemon list:

DAEMONS=(syslog-ng dbus wicd @acpid @laptop-mode @cupsd @cpufreq @ntpd @crond)

--
Neal

Sorry. My fault. That output was pasted after my last try without dbus.
Normaly it looks like this

DAEMONS=(syslog-ng dbus @wicd @ntpd @alsa @sshd)

HuckleSmothered

Member

Registered: 2010-03-25

Posts: 68

Re: Login prompt mixed up with daemons

I'm having this same problem, actually.
Here's my daemons line in /etc/rc.conf:

DAEMONS=(dbus @hwclock @syslog-ng @wicd @wicd-gtk !wireless-regdom !network @alsa @netfs @openntpd @crond)

Last edited by HuckleSmothered (2011-11-06 18:10:19)

HeSaid

Member

From: southwest Florida USA

Registered: 2010-07-02

Posts: 53

Re: Login prompt mixed up with daemons

You should remove wicd-gtk from daemon list.  It is not a daemon. 
--
Neal

---

Registered Linux User 159445.

manzdagratiano

Member

From: New Jersey, USA

Registered: 2010-10-08

Posts: 137

Re: Login prompt mixed up with daemons

This is extremely weird - all my daemons are started right after "Waiting for udev to process events" and right before the login prompt. Here's my daemons array:

DAEMONS=(!hwclock @syslog-ng dbus !network netfs @crond wicd @alsa gdm @cupsd @sshd @sshguard @iptables)

Does the order in which the events are executed matter here?

---

Be formless, shapeless... like water. Now you put water into a cup, it becomes the cup; you put water into a bottle it becomes the bottle; if you put it in a teapot it becomes the teapot... Now water can flow, or it can crash... Be water my friend

dudko

Member

Registered: 2010-03-04

Posts: 41

Re: Login prompt mixed up with daemons

Any new ideas in my case?:)

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: Login prompt mixed up with daemons

Radioactiveman posted this: https://bbs.archlinux.org/viewtopic.php … 5#p1034095
I was able to replicate your issues when I changed 'wait' to 'once' in inittab, so maybe this is it.

dudko

Member

Registered: 2010-03-04

Posts: 41

Re: Login prompt mixed up with daemons

Radioactiveman posted this: https://bbs.archlinux.org/viewtopic.php … 5#p1034095
I was able to replicate your issues when I changed 'wait' to 'once' in inittab, so maybe this is it.

thanks.:)
I've already reinstalled whole system, so I can't confirm that solution.
wish you good luck.

HuckleSmothered

Member

Registered: 2010-03-25

Posts: 68

Re: Login prompt mixed up with daemons

I also ended up reinstalling my system the other day (for other reasons). The new install does not have this problem.

However, I was playing with the /etc/inittab file before reloading. It was already at 'wait'. Which kind of invalidates that solution for my situation. I did, just for kicks, try 'once' instead and nothing changed, go figure.

I compared my new /etc/inittab with my old one. Almost identical. The only difference was the "active consoles" section. The new one has a '-s' option on /sbin/agetty whereas my old one did not.