On 03/26/2018 12:30 PM, Frank Filz wrote: >> FYI—— >> >> SEGV when parsing a bad ganesha.conf. >> >> This is version 2.4.5 (!!!) from the CentOS Storage SIG. >> >> core and config files are not available. :-( > > Any way we can figure out the config that caused this?
Er, no. > Who ran this test? We could throw that config at V2.4-stable and see if it > crashes there. It's not a test. There are coming from systems running ganesha out in the wild. When anything crashes the ABRT daemon phones home to Fedora. Everything that's available is at the link I forwarded, which is only the bt. Any more than that would likely be considered a potential security breach if the ABRT daemon automatically sent it; config files and core files could contain hostnames and/or other sensitive info. This is CentOS (and Fedora) boxes running the community/free packages. The paying customers will have support people filing BZs and getting full up SOS reports from the crashes. (And I don't even know if Debian, Ubuntu, and SuSE have anything resembling ABRTd.) -- Kaleb ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
