Slackware current

Woodsman · 10-13-2008, 06:31 PM

I notice in slackware current that some code was added to rc.6 and rc.K to stop the acpi daemon. Sounds great as I have had this in my rc.shutdown script for several years. However, I notice some differences that puzzle me.

First, rc.K uses the following:

Code:

# Terminate acpid before syslog:
if ps axc | grep -q bin/acpid ; then
  killall -SIGQUIT acpid
fi

rc.6 uses the following:

Code:

if [ -x /etc/rc.d/rc.acpid -a -r /var/run/acpid.pid ]; then # quit
  /etc/rc.d/rc.acpid stop
fi

I realize the two scripts have slightly different purposes, but why the difference? Why not call /etc/rc.d/rc.acpid stop in rc.K?

Second, I have no /var/run/acpid.pid file. I have a /var/run/acpid.socket. Therefore the code in rc.6 always will fail to execute on my box. I checked man acpid and found no reference to a PID file.

Third, rc.K uses killall -SIGQUIT acpid while rc.acpid uses killall acpid. Why the difference?

None of this is shattering or a deal breaker. I can modify the scripts if I choose. Yet perhaps somebody can explain the differences?

Thanks.

niels.horn · 10-15-2008, 07:21 AM

I use -current and do have the /var/run/acpid.pid file, with the correct process ID.

The difference between kill with SIGTERM (default if you do not specify a signal) and SIGQUIT is like the difference between "Could you please leave?" and "Exit now!"

Woodsman · 10-15-2008, 08:03 PM

Well, golly gee willikers Mr. Wilson!! Yes I have an acpid.pid file too --- in current. I mistakenly wrote my post while in 12.1 after running current. The 12.1 version of acpid has no PID file. So "never mind" on that "observation."