<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Michael<br><br><div><br></div></div><blockquote type="cite"><div><span></span><span>b/ acpid's internal event processing which calls (shell) scripts on</span><br><span>certain events which are defined in /etc/acpi/.</span><br></div></blockquote><div><br></div>Yes, that one.<div><br><blockquote type="cite"><div><span></span><span>I assume Norbert is using acpid in mode b/, so what he noticed was, that</span><br><span>his shell scripts in /etc/acpi/ were not processed as he apparently</span><br><span>doesn't have a service which triggers the start of acpid by reading from</span><br><span>/run/acpid.socket.</span><br></div></blockquote><div><br></div>Yes, because they are response scripts to simple key press events toggling the touchpad - a 5 liner in shell script.</div><div><br></div><div>I think there should be no need for a special service for that.</div><div><br></div><div>Amd, out of pure and simply consistency during upgrades, acpid *has* to run. I am not the only one relying on acpi scripts I guess.</div><div><br></div><div>Norbert<br><div><br></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">------------------------------------------------------------------------</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">PREINING, Norbert <a href="http://www.preining.info/">http://www.preining.info</a></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">JAIST, Japan TeX Live & Debian Developer</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">------------------------------------------------------------------------</span></div></div><div><br></div></div></body></html>