Arch Linux

alleluia20

Member

Registered: 2009-04-13

Posts: 53

Firestarter fails to start as a daemon, any way to keep retrying?

Hello,

I connect via wifi using network-manager (the connection starts even before logging into the desktop, it was like that at least the day I tested it). This is my daemons line in /etc/rc.conf:

DAEMONS=(syslog-ng hal laptop-mode cpufreq !network dhcdbd networkmanager netfs firestarter fail2ban cups fcron alsa)

At boot, "starting failstarter" fails. If I do ps, I cannot see firestarter. It only starts running when I log into the desktop, and launch firestarter's gui as root. So this kind of protection is not good, because other users do not have the root password and/or may forget to start firestarter's gui.

Any ideas why firestarter fails to start as a daemon?

Thank you very much in advance.

Last edited by alleluia20 (2009-05-24 17:54:35)

alleluia20

Member

Registered: 2009-04-13

Posts: 53

Re: Firestarter fails to start as a daemon, any way to keep retrying?

Well, after logging into the desktop and doing
# /etc/rc.d/firestarter start
it starts. So I assume it did not start at boot because the network was not ready.

Is there any way to set rc.conf so that the daemons that failed to start keep retrying?

Thank you.

jwcxz

Member

Registered: 2008-09-23

Posts: 239

Website

Re: Firestarter fails to start as a daemon, any way to keep retrying?

You can use networkmanager-dispatcher to start a service once the network is up and shut it down when the network is down.  I haven't used NM in a while, but I think there is documentation on the Arch wiki.

---

-- jwc
http://jwcxz.com/ | blog
dotman - manage your dotfiles across multiple environments
icsy - an alarm for powernappers

alleluia20

Member

Registered: 2009-04-13

Posts: 53

Re: Firestarter fails to start as a daemon, any way to keep retrying?

Strange, I tried the dispatcher with firestarter and fail2ban. The latter starts but the former doesn't. Why? Is firestarter so faulty?

alun

Member

Registered: 2009-05-24

Posts: 8

Re: Firestarter fails to start as a daemon, any way to keep retrying?

Yes, I believe so. I haven't checked in a while, but it seems to me that firestarter development halted completely a few years ago.

alleluia20

Member

Registered: 2009-04-13

Posts: 53

Re: Firestarter fails to start as a daemon, any way to keep retrying?

Thank you. So, which firewall would you recommend for a laptop with network-manager (that may connect through different things: cable, wifi, 3G, etc), you can use without being an ip-tables guru, and unblocks the ports/services that your running applications are using?

Thank you very much.

alun

Member

Registered: 2009-05-24

Posts: 8

Re: Firestarter fails to start as a daemon, any way to keep retrying?

Might I suggest Ubuntu's gufw? I've never actually used it, but it's available in the repos and it's an Ubuntu app so it sounds like it would suit your needs.

I used to use the shorewall configuration scripts, which are a lot easier than straight iptables but still all text. I later decided that a firewall is really unnecessary for a standard arch workstation.

alleluia20

Member

Registered: 2009-04-13

Posts: 53

Re: Firestarter fails to start as a daemon, any way to keep retrying?

Thank you! gufw looks great, although it is still pretty buggy (at least in Arch).

I later decided that a firewall is really unnecessary for a standard arch workstation.

Why is a firewall not necessary?
Not even in a laptop in which you may have sensitive data and with which you may connect to public wifis?

alun

Member

Registered: 2009-05-24

Posts: 8

Re: Firestarter fails to start as a daemon, any way to keep retrying?

I'm not that sure, really. Total networking noob speaking here, but I just figured it won't matter what ports get hit so long as there are no server processes waiting on them.

Don't take my word for it.

Correct me ASAP if I'm wrong, please.

Last edited by alun (2009-05-25 05:22:00)