ZH> $ sudo systemctl stop acpid
ZH> Job for acpid.service canceled.
... because, as noted, it's a socket-activated service, which actually
makes it two separately startable and stoppable things
("acpid.service" and "acpid.socket") in the world of systemd, only one
of which is being stopped when yo
Bug #736258 reopened, set to severity grave, and reassigned to systemd for
further processing and action.
Full explanation added to the bug report and CC'd to the bug report and to
the systemd maintainers.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and i
Hi
Am 26.07.2014 19:44, schrieb Henrique de Moraes Holschuh:
> Since just about everything in a "modern desktop" will pester the acpi
> netlink socket, please ask a systemd expert whether "systemctl stop"
> *blocks* socket activation of that service until further notice, or not.
> If it doesn't
On Sat, 26 Jul 2014, Zenaan Harkness wrote:
> Interrelated problem A:
> $ ps aux|egrep -i acpid
> root 318 0.0 0.0 0 0 ?S< 12:40 0:00 [ktpacpid]
> root 19855 0.0 0.0 4372 972 ?Ss 17:45 0:00
> /usr/sbin/acpid
> $ sudo systemctl stop acpid
> Job for
On Sun 04 Nov 2012 at 15:07:03 +, T o n g wrote:
> Would acpi-support conflict with acpid?
No. acpid is a daemon which runs scripts. It doesn't provide the
scripts. That is the job of other packages.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsub
On 2012-09-14 13:28, Camaleón wrote:
On Fri, 14 Sep 2012 08:48:11 -0400, Chris Capon wrote:
On 2012-09-13 13:07, Camaleón wrote:
On Wed, 12 Sep 2012 14:54:20 -0400, Chris Capon wrote:
After a recent Debian update, I've been unable to log in to my
Debian/Linux server using the console and GDM
On Fri, 14 Sep 2012 08:48:11 -0400, Chris Capon wrote:
> On 2012-09-13 13:07, Camaleón wrote:
>> On Wed, 12 Sep 2012 14:54:20 -0400, Chris Capon wrote:
>>
>>> After a recent Debian update, I've been unable to log in to my
>>> Debian/Linux server using the console and GDM3 won't start - X.org
>>> c
On 2012-09-13 13:07, Camaleón wrote:
On Wed, 12 Sep 2012 14:54:20 -0400, Chris Capon wrote:
After a recent Debian update, I've been unable to log in to my
Debian/Linux server using the console and GDM3 won't start - X.org
crashes part way through the startup.
What can be read from X server err
On Wed, 12 Sep 2012 14:54:20 -0400, Chris Capon wrote:
> After a recent Debian update, I've been unable to log in to my
> Debian/Linux server using the console and GDM3 won't start - X.org
> crashes part way through the startup.
What can be read from X server error logs?
(you can boot from singl
Quoth green at 12/10/09 11:10...
Perhaps you need to look at acpid(8). Find out what the initscript is using,
and try running acpid manually with some of --debug, --foreground, --logevents.
Well, that's interesting:
vaio:/etc/init.d# acpi_listen
acpi_listen: can't open socket /var/run/acpid.s
Quoth Alex Samad at 2009-10-13 08:06...
> maybe have alook at acpi_listen to see if acpi is getting the event
Thanks - sounds like an easier way than wading through logs. Another
useful programme for my toolkit.
Cheers
M
--
Matthew Smith
Smiffytech - Technology Consulting & Web Application D
On Mon, Oct 12, 2009 at 12:34:15PM +1030, Matthew Smith wrote:
> Quoth green at 2009-10-12 11:10...
> > Perhaps you need to look at acpid(8). Find out what the initscript is
> > using,
> > and try running acpid manually with some of --debug, --foreground,
> > --logevents.
>
> Thanks, will do o
Matthew Smith wrote at 2009-10-11 21:04 -0500:
> I plan to do more with acpi (like running s2disk when the battery gets
> to a certain level) so really need to get that logging sorted.
In case you are interested, sleepd will do that for you.
signature.asc
Description: Digital signature
Quoth green at 2009-10-12 11:10...
> Perhaps you need to look at acpid(8). Find out what the initscript is using,
> and try running acpid manually with some of --debug, --foreground,
> --logevents.
Thanks, will do once I've got the machine re-installed.
I plan to do more with acpi (like runnin
Matthew Smith wrote at 2009-10-10 21:05 -0500:
> The problem that I'm having is that modifying /etc/acpi/powerbtn.sh or
> /etc/acpi/powerbtn-acpi-support.sh seems to have no effect. After
> restarting acpid, pressing the button has no effect at all - neither the
> one in the original version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Byron Watkins wrote:
> I am running Debian testing on amd64. About a week ago acpid began
> reporting an error status whenever I "apt-get upgrade" or use synapsis
> from gnome:
>
> Setting up acpid (1.0.4-7.1) ...
> Loading ACPI modules
> Startin
16 matches
Mail list logo
