This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug releng/20889] New: metadatabase.db location
- From: "mcermak at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 30 Nov 2016 17:40:40 +0000
- Subject: [Bug releng/20889] New: metadatabase.db location
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20889
Bug ID: 20889
Summary: metadatabase.db location
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: releng
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
When systemtap gets RPM packaged using `make rpm`, the metadatabase.db file
effectively gets copied to 2 locations (and gets a part of two subrpms) at the
specfile's %install section:
=======
7.3 Server x86_64 # locate metadatabase.db
/usr/share/doc/systemtap-client-3.1/examples/metadatabase.db
/usr/share/systemtap/testsuite/systemtap.examples/metadatabase.db
7.3 Server x86_64 # rpm -qf --queryformat='%{name}\n' `locate metadatabase.db`
systemtap-client
systemtap-testsuite
7.3 Server x86_64 #
=======
But stap in the interactive mode searches for it in
/usr/share/doc/systemtap/examples/metadatabase.db so that the user gets an
error:
=======
7.3 Server x86_64 # stap -i
Example commands: 'sample', 'add', 'run', 'help'
stap> sample socket AND tcp* OR disk NOT virtual
Error connecting to meta database. RC: 14
stap>
=======
--
You are receiving this mail because:
You are the assignee for the bug.