#177 oparchive looks for daemon log in the wrong place

[Jim Blandy]

oparchive assumes that the daemon log is named /var/lib/oprofile/oprofiled.log, but it's actually named /var/lib/oprofile/samples/oprofiled.log:

$ sudo opcontrol --start
Using default event: CPU_CLK_UNHALTED:100000:0:1:1
Using 2.6+ OProfile kernel interface.
Using log file /var/lib/oprofile/samples/oprofiled.log
Daemon started.
Profiler running.
$

This results in an error message:

$ oparchive -o foon
can't copy from /var/lib/oprofile/oprofiled.log to foon/var/lib/oprofile/oprofiled.log cause: No such file or directory
$

even though the log is there, in the samples subdirectory:

$ ls /var/lib/oprofile/samples/
current oprofiled.log
$

[Jim Blandy]

In the current sources, oparchive still looks for oprofiled.log in /var/lib/oprofile, even when passed a --session-dir argument.

[Maynard Johnson]

A fix for this bug was posted to the oprofile-list on May 7, with subject heading:
[PATCH] Fixes for oparchive session-dir as reported in bugs 2646389 and 2646376

[Maynard Johnson]

A fix for this was committed to CVS today.