Hi @emitorino, thanks for replying again.
So it seems snaps aren’t well suited for system management utilities, at least where there isn’t a finite list of locations.
Would it be reasonable to use system-files to list the default locations of mysql/mariadb/postgres, even though my app isn’t the owner of those locations? Even then the utility would be limited, as it’s common for databases to have non-default locations.
Below is an example use case, where I check to see how much of my mysql DB files are resident in memory. You can see that even as root, I can’t map the DB files. I can bypass the snap link and run the executable that way, but that defeats the purpose, and I wouldn’t want to include a hack like that in the man page.
Thanks for your help!
Tim
root@kinetic:~# type mincore
mincore is /snap/bin/mincore
root@kinetic:~# mincore /var/lib/mysql/ib*
pages pages not %
in core in core in file
---------- ---------- ---- --------------------
- /var/lib/mysql/ib_buffer_pool: No such file or directory
- /var/lib/mysql/ibdata1: No such file or directory
- /var/lib/mysql/ib_logfile0: No such file or directory
- /var/lib/mysql/ibtmp1: No such file or directory
---------- ---------- ---- --------------------
0 0 0 total pages
0.0 0.0 total MB (4kb pages)
root@kinetic:~# /snap/mincore/current/usr/bin/mincore /var/lib/mysql/ib*
pages pages not %
in core in core in file
---------- ---------- ---- --------------------
1 0 100 /var/lib/mysql/ib_buffer_pool
1520 1552 49 /var/lib/mysql/ibdata1
21 12267 0 /var/lib/mysql/ib_logfile0
3072 0 100 /var/lib/mysql/ibtmp1
---------- ---------- ---- --------------------
4614 26107 15 total pages
18.0 102.0 total MB (4kb pages)
root@kinetic:~#