[mylvmbackup] innodb_recover bug, related to pid (0.6 release)

I'd like to submit a but report concerning mylvmbackup. On CentOS 5.1, I stubbled on this error :
If you activate the innodb_recover option, the mysql_safe thread that intend to run the innodb restoration use the --pidfile option which is not valid. Hence the server starts with default pid file, which is already in use. 

> A mysqld process already exists

To correct this, you'd need to correct the mylvmbackup script at line 497
> if ( system("echo 'select 1;' | $mysqld_safe --pidfile=$pidfile --datadir=$mountdir --skip-networking --skip-grant --bootstrap --skip-ndbcluster --skip-slave-start") != 0 ) 
for :
> if ( system("echo 'select 1;' | $mysqld_safe --pid-file=$pidfile --datadir=$mountdir --skip-networking --skip-grant --bootstrap --skip-ndbcluster --skip-slave-start") != 0 )
the correct pidfile flag for mysqld (on my CentOS box at least) is --pid-file not --pidfile. 

Thanks for this useful tool !

--
Guillaume Boddaert

Other related posts: