Many times, there are slight inconsistencies between two similar linux machines, where (for example) tmux supports colours on Machine M1, and does not support colours on Machine M2, or vi adds comments and formatting automatically on M1 but not on M2, or bash prompt has line-warping on or off, ssh options may not match.Usually, we can try strace bash or strace ssh or ssh -vvv and man vi and look for standard files getting accessed.But , in nonstandard installations , (including customised compilations) these locations may not be complete.In some cases, we can not even use strace or pass verbose options, eg logon shells, or some script calling some other scripts which call the tool in question.So my question is : is there any standard method and tool which can help in finding all configuration files accessed by some tool ?Specific example : on M1, bash has line-warp, while on M2, it does not, even though all relevant parameters/files (.bashrc/.inputrc) are as expected and same on both M1 and M2.
How to generate a list of configuration files accessed by a tool (eg bash or vi)?
command line;debugging
Based on a comment by @0xC0000022L , I found http://security.blogoverflow.com/2013/01/a-brief-introduction-to-auditd/ which seems to be useful, so adding it as a community wiki answer, in case other folks search for such questions ; I would not want them to simply move on, thinking that there was no answer here.