Description of problem:

# /usr/sbin/acpid -f -d -d -d -l
acpid: proc fs opened successfully
acpid: starting up with proc fs
acpid: skipping conf file /etc/acpi/events/video.conf
acpid: skipping conf file /etc/acpi/events/..
acpid: skipping conf file /etc/acpi/events/.
acpid: skipping conf file /etc/acpi/events/power.conf
acpid: 0 rules loaded

Looking at the source, we find this in events.c:

        /* Compile the regular expression.  This is based on run-parts(8). */
        rc = regcomp(&preg, "^[a-zA-Z0-9_-]+$", RULE_REGEX_FLAGS);
...

                /* skip any files that don't match the run-parts convention */
                if (regexec(&preg, dirent->d_name, 0, NULL, 0) != 0) {
                        acpid_log(LOG_DEBUG, "skipping conf file %s/%s\n",
                                confdir, dirent->d_name);
                        continue;
                }

Unfortunately, since power.conf and video.conf as shipped have a '.' in the filename and the regexp doesn't, they get skipped.

Is this a new thing that the sysadmin needs to rename the *.conf files in order to make them start working?

In addition, the "run-parts convention" seems to be something other than what that regexp actually implements - /usr/bin/run-parts has this:

for i in $(LC_ALL=C; echo $1/*[^~,]) ; do
        [ -d $i ] && continue
        # Don't run *.{rpmsave,rpmorig,rpmnew,swp,cfsaved} scripts
        [ "${i%.cfsaved}" != "${i}" ] && continue
        [ "${i%.rpmsave}" != "${i}" ] && continue
        [ "${i%.rpmorig}" != "${i}" ] && continue
        [ "${i%.rpmnew}" != "${i}" ] && continue
        [ "${i%.swp}" != "${i}" ] && continue
        [ "${i%,v}" != "${i}" ] && continue

In particular, those 'continue' are a bunch more specific than what the regexp does.

Version-Release number of selected component (if applicable):
acpid-2.0.3-1.fc14.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: