Menu

#3 Lighten up on the conf check in Coati.pm

open
nobody
None
5
2009-02-23
2009-02-23
jinman
No

I'm running an initdb component in ergatis and the checkDatabase.pl script was having trouble.

A little digging uncovered a bug in Coati::Coati::parse_config where if the .conf file (in this case Prism.conf) is not present, the script dies at get_config_path before existing code parse_config can check for and use the $altconfig (in this case the $ENV{PRISM} var that gets exported by the wrapper to checkDatabase.pl)

The offending lines reporting the $msg:
Can't find $config_basename in current working directory or perl search path
should be changed to non-fatal reporting.

Thanks!
Jason

Discussion

MongoDB Logo MongoDB