Greetings all...
This would be a suggestion and an alert to newbies, like myself:
By following the README.txt upgrading from 1.22.1 to 1.22.3 i found a problem with the zmupdate.pl script.
After the "make install" a new /usr/local/etc/zm.conf is created and this do not respect my old one that has a different
ZM_DB_USER and ZM_DB_PASS than the default:
ZM_DB_USER=zmuser
ZM_DB_PASS=zmpass
This is because the zm.conf that is in the ZM source tree has a zm.conf with those defaults...
The catch is that even by doing this:
./scripts/zmupdate.pl -version=1.22.1 --user=xxxxxx --pass=yyyyyy
this info about user and pass is not being inserted in the new /usr/local/etc/zm.conf and by doing so, the upgrade process perl script fails to access the SQL database.
My suggestion is that the zmupdate.pl do not alter an existing /usr/local/etc/zm.conf if such is already existent.
Upgrades and the zm.conf file
Upgrades and the zm.conf file
The fact is a secondary aspect of Reality.
Maybe i am doing something wrong...
From my experience, each time one do a "make install" the zm.conf in use is replaced by a new one and the user/pass settings to access the database are changed to the default.
I am following step-by-step the README procedures...
I am following step-by-step the README procedures...
The fact is a secondary aspect of Reality.
The command i use is:
./configure --with-webuser=apache --with-webgroup=apache \ --with-webdir=/var/www/htdocs --with-cgidir=/var/www/cgi-bin
and the result is that i told before...
Do you mean that, for instance, one _must_ do this first?
export ZM_DB_USER=apache
export ZM_DB_PASS=sql_pass
before start the "./configure " command ??
./configure --with-webuser=apache --with-webgroup=apache \ --with-webdir=/var/www/htdocs --with-cgidir=/var/www/cgi-bin
and the result is that i told before...
Do you mean that, for instance, one _must_ do this first?
export ZM_DB_USER=apache
export ZM_DB_PASS=sql_pass
before start the "./configure " command ??
The fact is a secondary aspect of Reality.
./configure --with-webuser=apache --with-webgroup=apache \ --with-webdir=/var/www/htdocs --with-cgidir=/var/www/cgi-bin \
ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser \ ZM_DB_PASS=zmdbuserpass
As described in the README and from ./configure --help
Or there is always the alternative of making a backup ie.
cp zm.conf zm.conf.bak
then replace the new config after install
cp zm.conf.bak zm.conf
ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=zmuser \ ZM_DB_PASS=zmdbuserpass
As described in the README and from ./configure --help
Or there is always the alternative of making a backup ie.
cp zm.conf zm.conf.bak
then replace the new config after install
cp zm.conf.bak zm.conf
OK - now i understood
The point is that i was mislead by what "./configure --help" tells:
Some influential environment variables:
ZM_DB_HOST Hostname where ZoneMinder database located
ZM_DB_NAME Name of ZoneMinder database
ZM_DB_USER Name of ZoneMinder database user
ZM_DB_PASS Password of ZoneMinder database user
For me, "environment variables" is different from "passed parameters".
Anyway, i feel that "make install" should create a new zm.conf, like in zm.conf-new and do not mess at all with one already existing zm.conf in the system.
Thanks Cordel...
Some influential environment variables:
ZM_DB_HOST Hostname where ZoneMinder database located
ZM_DB_NAME Name of ZoneMinder database
ZM_DB_USER Name of ZoneMinder database user
ZM_DB_PASS Password of ZoneMinder database user
For me, "environment variables" is different from "passed parameters".
Anyway, i feel that "make install" should create a new zm.conf, like in zm.conf-new and do not mess at all with one already existing zm.conf in the system.
Thanks Cordel...
The fact is a secondary aspect of Reality.