Page History

...

 The local offline processes LDF into digi and uses calibrations that are installed in the SLAC database to produce reconstructed and high level data analysis files. The goal is to have a way to quick debug and characterize the beam during the set-up.  If there is a copy of the database locally then we can use it to process events much fastereven when the connection to SLAC is down.

There will also be an offline monitoring running locally. 

Computer names in the PS area

...

Describes policy and steps for updating. When things become stable we will have a CCB.

Policy for Reprocessing

Describes policy and steps for reprocessing. When things become stable we will have a CCB.

Environmental Variables for Database

...

mysql> grant usage on . to glastreader@localhost identified by 'glastpassword';
mysql> grant select on calib.* to glastreader@localhost identified by 'glastpassword';
(and maybe...)
mysql> grant usage on . to glastreader@"%" identified by 'glastpassword';
mysql> grant select on calib.* to glastreader@"%" identified by 'glastpassword';
mysql> select host, user, password from mysql.user;
------------------------------

------------------------------

------------------------------
6 rows in set (0.00 sec)
'xxxx...' is the encrypted form of the password you just typed in... Actually, it's not 'xxxx...' but I x'ed it out so you wouldn't see it. It's what MySQL uses to check the plaintext password. The password 'glastpassword' is the same one that you got from Leon or Joanne, above.

You also want to protect your 'root' user with a password:mysql>set password for root@localhost = password('mynewpassword');
Query OK...
mysql> set password for root@"%" = password('mynewpassword');
Query OK...
mysql> select host, user, password from mysql.user;
------------------------------

------------------------------

------------------------------
6 rows in set (0.00 sec)

The "password('mynewpassword')" is very important... it does the encryption. If you leave it out, mysql> set password for root@"%" = 'mynewpassword';
ok...
it doesn't get encrypted, and MySQL won't recognize it when you try to login.

Finally, if you see a blank user, you should get rid of it:mysql%gt delete from mysql.user where host='localhost' and user="";
Query OK...
mysql%gt delete from mysql.user where host="&" and user="";
Query OK...
mysql> select host, user, password from mysql.user;
------------------------------

------------------------------

------------------------------
4 rows in set (0.00 sec)

That's better!

...