Bug 824007

Description of problem:

According to the old logging specification it should be possible to:

logging {
        # Log the source file and line where messages are being
        # generated. When in doubt, leave off. Potentially useful for
        # debugging.
        fileline: off
        # Log to standard error. When in doubt, set to no. Useful when
        # running in the foreground (when invoking "corosync -f")
        to_stderr: yes
        # Log to a log file. When set to "no", the "logfile" option
        # must not be set.
        to_logfile: yes
        logfile: /var/log/cluster/corosync.log
        # Log to the system log daemon. When in doubt, set to yes.
        to_syslog: yes
        # Log debug messages (very verbose). When in doubt, leave off.
        debug: off
        # Log messages with time stamps. When in doubt, set to on
        # (unless you are only logging to syslog, where double
        # timestamps can be annoying).
        timestamp: on
        logger_subsys {
                subsys: QUORUM
                debug: on
        }
        logger_subsys {
                subsys: VOTEQ
                debug: on
        }
        logger_subsys {
                subsys: QDISKD
                debug: on
                logfile: /var/log/cluster/test.log
        }
}

and have QDISKD subsystem use /var/log/cluster/test.log

The configuration is loaded, 2 files are created when starting up corosync:

[root@fedora-master-node2 cluster]# ls -las
total 8
4 drwxr-xr-x   2 root root 4096 May 22 16:39 .
4 drwxr-xr-x. 11 root root 4096 May 22 15:23 ..
0 -rw-r--r--   1 root root    0 May 22 16:39 corosync.log
0 -rw-r--r--   1 root root    0 May 22 16:39 test.log

but both files will always stay at 0 bytes, no matter how much logging is enabled.

Version-Release number of selected component (if applicable):

[root@fedora-master-node2 cluster]# rpm -q -i libqb
Name        : libqb
Version     : 0.13.0
Release     : 1.fc18

corosync built from git master

How reproducible:

always

Steps to Reproduce:
1. configure the above
2. start corosync
3.


Additional info: