Arch Linux

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

[SOLVED] Acpid isn't getting launched properly

I have a problem with acpid: it won't launch correctly at boot. I firstly have to stop the daemon, and then start it again, to get it to work.

Here's my DAEMON array from /etc/rc.conf:

DAEMONS=(dbus acpid @networkmanager @cpufreq @hwclock @syslog-ng)

I don't know what could cause this, can any of you help me?

Last edited by Unia (2011-07-05 11:20:33)

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

ConnorBehan

Package Maintainer (PM)

From: Long Island NY

Registered: 2007-07-05

Posts: 1,359

Website

Re: [SOLVED] Acpid isn't getting launched properly

If you remove acpid from your rc.conf and only load it from the tty, does it still take two tries to start?

One thing you should always try is making the problematic daemon the last one in the list (and disable background loading) in case it depends on other daemons that haven't started yet. Once that works you can try to progressively push it into the earlier parts of the list.

---

6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

If you remove acpid from your rc.conf and only load it from the tty, does it still take two tries to start?

Nope, so I guess it does rely on an other daemon then. This is not stated in the wiki, however.

One thing you should always try is making the problematic daemon the last one in the list (and disable background loading) in case it depends on other daemons that haven't started yet. Once that works you can try to progressively push it into the earlier parts of the list.

I will now try that and see what I come up with. I'll report back once I got something (or nothing)

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

Ok so I just edited my DAEMONS array to look like this:

DAEMONS=(dbus networkmanager cpufreq hwclock syslog-ng acpid)

But still, when I reboot, I have to manually stop and start the acpid daemon again in order to get it to function properly. What is going on here?

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

When I google around on this issue, it always is related to hald (hal?) starting earlier than acpid. However, I don't have hald (hal?) installed.

EDIT: Placing acpid in front of the DAEMONS array doesn't solve the issue either. It seems like it's not another daemon causing this, but something within acpid itself. Anyone?

Last edited by Unia (2011-07-03 21:03:55)

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

nc

Member

From: Braga, Portugal

Registered: 2009-04-08

Posts: 20

Re: [SOLVED] Acpid isn't getting launched properly

Same problem here. I need to manually restart acpi to get it to funtion properly. My daemons array:

DAEMONS=(syslog-ng dbus acpid @wicd @laptop-mode)

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

Glad I'm not alone on this. Maybe there's something wrong with the package?

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

Lone_Wolf

Forum Moderator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,969

Re: [SOLVED] Acpid isn't getting launched properly

No problems with acpid here : 

DAEMONS=(!hwclock syslog-ng network netfs cpufreq ntpd dbus @acpid @alsa @cups @vsftpd @crond)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

Maybe it's the version then? I have acpid 2.0.10-2

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

Lone_Wolf

Forum Moderator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,969

Re: [SOLVED] Acpid isn't getting launched properly

same version as i have, it's probably hardware or bios related .
Check your /var/log/daemon.log

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

I also noticed there's a /var/log/acpid.log. That file contains this for today:

Jul  4 13:45:08 localhost acpid: client connected from 1332[0:0]
Jul  4 13:45:08 localhost acpid: 1 client rule loaded

/var/log/daemon.log contains this for today (I *censored* all network stuff):

Jul  4 00:37:01 localhost ntfs-3g[25020]: Version 2011.4.12 external FUSE 28
Jul  4 00:37:01 localhost ntfs-3g[25020]: Mounted /dev/sdc1 (Read-Write, label "HDD", NTFS 3.1)
Jul  4 00:37:01 localhost ntfs-3g[25020]: Cmdline options: rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=100,dmask=0077,fmask=0177
Jul  4 00:37:01 localhost ntfs-3g[25020]: Mount options: rw,nosuid,nodev,uhelper=udisks,allow_other,nonempty,atime,fsname=/dev/sdc1,blkdev,blksize=4096,default_permissions
Jul  4 00:37:01 localhost ntfs-3g[25020]: Global ownership and permissions enforced, configuration type 1
Jul  4 00:47:26 localhost ntfs-3g[25020]: Unmounting /dev/sdc1 (HDD)
Jul  4 00:49:41 localhost NetworkManager[1824]: <info> (wlan0): supplicant interface state: completed -> disconnected
Jul  4 00:49:41 localhost NetworkManager[1824]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Jul  4 00:49:42 localhost NetworkManager[1824]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Jul  4 00:49:42 localhost NetworkManager[1824]: <info> (wlan0): supplicant interface state: authenticating -> associating
Jul  4 00:49:42 localhost NetworkManager[1824]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Jul  4 00:49:43 localhost NetworkManager[1824]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Jul  4 01:36:19 localhost init: Switching to runlevel: 0
Jul  4 13:45:07 localhost [    1.314883] udevd[114]: starting version 171
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> NetworkManager (version 0.8.9997) is starting...
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Jul  4 13:45:07 localhost [    5.347336] udevd[468]: starting version 171
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Jul  4 13:45:07 localhost NetworkManager[1312]:    keyfile: parsing *censor* ... 
Jul  4 13:45:07 localhost NetworkManager[1312]:    keyfile:     read connection '*censor*'
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> trying to start the modem manager...
Jul  4 13:45:07 localhost dbus[1222]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jul  4 13:45:07 localhost polkitd[1325]: started daemon version 0.101 using authority implementation `local' version `0.101'
Jul  4 13:45:07 localhost dbus[1222]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> monitoring kernel firmware directory '/lib/firmware'.
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> found WiFi radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:05:00.0/ieee80211/phy0/rfkill0) (driver (unknown))
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> WiFi enabled by radio killswitch; enabled by state file
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> WWAN enabled by radio killswitch; enabled by state file
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> WiMAX enabled by radio killswitch; enabled by state file
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> Networking is enabled by state file
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> (eth0): carrier is OFF
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> (eth0): new Ethernet device (driver: 'tg3' ifindex: 2)
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> (eth0): now managed
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jul  4 13:45:07 localhost NetworkManager[1312]: <info> (eth0): bringing up device.
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (eth0): preparing device.
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (eth0): deactivating device (reason: 2).
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:1c.0/0000:03:00.0/net/eth0
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): now managed
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): bringing up device.
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): preparing device.
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): deactivating device (reason: 2).
Jul  4 13:45:08 localhost dbus[1222]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
Jul  4 13:45:08 localhost NetworkManager[1312]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Jul  4 13:45:08 localhost dbus[1222]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> wpa_supplicant started
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): supplicant interface state: starting -> ready
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jul  4 13:45:08 localhost NetworkManager[1312]: <info> (wlan0): supplicant interface state: ready -> inactive
Jul  4 13:45:08 localhost acpid: client connected from 1332[0:0]
Jul  4 13:45:08 localhost acpid: 1 client rule loaded
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Activation (wlan0) starting connection '*censor*'
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Activation (wlan0/wireless): connection '*censor*' has security, and secrets exist.  No new secrets needed.
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Config: added 'ssid' value '*censor*'
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Config: added 'scan_ssid' value '1'
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Config: added 'psk' value '<omitted>'
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> Config: set interface ap_scan to 1
Jul  4 13:45:09 localhost NetworkManager[1312]: <info> (wlan0): supplicant interface state: inactive -> scanning
Jul  4 13:45:10 localhost NetworkManager[1312]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> (wlan0): supplicant interface state: authenticating -> associating
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network '*censor*'.
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> dhcpcd started with pid 1351
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jul  4 13:45:11 localhost dhcpcd[1351]: version 5.2.12 starting
Jul  4 13:45:11 localhost NetworkManager[1312]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Jul  4 13:45:11 localhost dhcpcd[1351]: wlan0: rebinding lease of *censor*
Jul  4 13:45:11 localhost dhcpcd[1351]: wlan0: acknowledged *censor* from *censor*
Jul  4 13:45:11 localhost dhcpcd[1351]: wlan0: checking for *censor*
Jul  4 13:45:16 localhost dhcpcd[1351]: wlan0: leased *censor* for 86400 seconds
Jul  4 13:45:16 localhost NetworkManager[1312]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Jul  4 13:45:16 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jul  4 13:45:16 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Jul  4 13:45:16 localhost NetworkManager[1312]: <info>   address *censor*
Jul  4 13:45:16 localhost NetworkManager[1312]: <info>   prefix *censor*
Jul  4 13:45:16 localhost NetworkManager[1312]: <info>   gateway *censor*
Jul  4 13:45:16 localhost NetworkManager[1312]: <info>   nameserver '*censor*'
Jul  4 13:45:16 localhost NetworkManager[1312]: <info>   domain name '*censor*'
Jul  4 13:45:16 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jul  4 13:45:16 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Jul  4 13:45:16 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Jul  4 13:45:17 localhost dbus[1222]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jul  4 13:45:17 localhost dbus[1222]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jul  4 13:45:17 localhost NetworkManager[1312]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Jul  4 13:45:17 localhost NetworkManager[1312]: <info> Policy set '*censor*' (wlan0) as default for IPv4 routing and DNS.
Jul  4 13:45:17 localhost NetworkManager[1312]: <info> Activation (wlan0) successful, device activated.
Jul  4 13:45:17 localhost NetworkManager[1312]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Jul  4 13:45:17 localhost dbus[1222]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jul  4 13:45:17 localhost dbus[1222]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jul  4 13:45:24 localhost dbus[1222]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Jul  4 13:45:26 localhost dbus[1222]: [system] Successfully activated service 'org.freedesktop.UPower'
Jul  4 13:45:30 localhost dbus[1222]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper)
Jul  4 13:45:31 localhost dbus[1222]: [system] Successfully activated service 'org.freedesktop.UDisks'

I don't see anything that could be wrong.

Last edited by Unia (2011-07-04 12:28:12)

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

Lone_Wolf

Forum Moderator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,969

Re: [SOLVED] Acpid isn't getting launched properly

Jul  4 00:21:48 localhost acpid: exiting
Jul  4 12:06:01 localhost acpid: starting up with proc fs
Jul  4 12:06:01 localhost acpid: 2 rules loaded
Jul  4 12:06:01 localhost acpid: waiting for events: event logging is off
Jul  4 12:08:23 localhost acpid: client connected from 1313[0:100]
Jul  4 12:08:23 localhost acpid: 1 client rule loaded

This is my acpid.log .

@ Unia :   Is this the same system where you had troible getting the sleep button to work ?

@ nc  : are you using  a laptop ?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

Yes it is, an Acer Aspire 5740g

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

nc

Member

From: Braga, Portugal

Registered: 2009-04-08

Posts: 20

Re: [SOLVED] Acpid isn't getting launched properly

It's an Asus N61. I have to manually restart acpi to get all my rules to work

xduugu

Member

Registered: 2008-10-16

Posts: 292

Re: [SOLVED] Acpid isn't getting launched properly

I do not have acpid in rc.conf, but instead start it in .xinitrc. As far as I remember, my X related rules needed a running X to get loaded correctly. Maybe the rules, your refer to, are X ones as well.

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

So how do you start it from .xinitrc then? And what rules do you have? I have only one rule that activates my log-out script when I press the power button - now that you mentioned it; it does need X for that.

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

xduugu

Member

Registered: 2008-10-16

Posts: 292

Re: [SOLVED] Acpid isn't getting launched properly

It's just

sudo /etc/rc.d/acpid restart &>/dev/null &

but I guess you have to create an autostart script if you are using a login manager.

My rules that require X are display toggling (for use with external screens) and disabling the active screen.

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

It's just

sudo /etc/rc.d/acpid restart &>/dev/null &

but I guess you have to create an autostart script if you are using a login manager.

My rules that require X are display toggling (for use with external screens) and disabling the active screen.

I guess it could be placed in say, OB's autostart file. My last question however: won't this need a root password? Or have you edited the sudoers file?

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

xduugu

Member

Registered: 2008-10-16

Posts: 292

Re: [SOLVED] Acpid isn't getting launched properly

Yeah, I'm using

xduugu ALL = NOPASSWD: /etc/rc.d/acpid restart

in sudoers.

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

I placed that with my own username in the sudoers file, but when I ran the command I got an error. I then tried start instead of restart and got the same error:

:: Starting acpid                                                       [FAIL]

I then tried this line in sudoers:

%wheel ALL=(ALL) NOPASSWD: /etc/rc.d/acpid start

Same deal - still a fail.

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

Stebalien

Member

Registered: 2010-04-27

Posts: 1,237

Website

Re: [SOLVED] Acpid isn't getting launched properly

Just in case, all NOPASSWD entries should be at the end of your sudoers file (or at least after all other conflicting rules).

---

Steven [ web : git ]
GPG:  327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C
Do not email: honeypot@stebalien.com

ferda

Member

Registered: 2010-02-05

Posts: 67

Re: [SOLVED] Acpid isn't getting launched properly

Try removing the cpufreq entry or put it in front of acpid, it should be started automatically.

xduugu

Member

Registered: 2008-10-16

Posts: 292

Re: [SOLVED] Acpid isn't getting launched properly

I placed that with my own username in the sudoers file, but when I ran the command I got an error. I then tried start instead of restart and got the same error:

:: Starting acpid                                                       [FAIL]

But as root, running /etc/rc.d/acpid works?

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

Just in case, all NOPASSWD entries should be at the end of your sudoers file (or at least after all other conflicting rules).

They are.

Try removing the cpufreq entry or put it in front of acpid, it should be started automatically.

I tried placing acpid in front of everything and at the back of everything, didn't work.

I placed that with my own username in the sudoers file, but when I ran the command I got an error. I then tried start instead of restart and got the same error:

:: Starting acpid                                                       [FAIL]

But as root, running /etc/rc.d/acpid works?

Yes, then it works.

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres

Unia

Member

From: Stockholm, Sweden

Registered: 2010-03-30

Posts: 2,486

Website

Re: [SOLVED] Acpid isn't getting launched properly

Ah, can't believe how stupid I have been! This thread remembered me I still have to use sudo. I shouldn't work on these things when I'm dead tired, sigh. Thanks all, problem is now solved!

---

If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres