Issue 327 in glassdb: need to drop note in object log that there is important info in a gems log file

Status: Accepted
Owner: [hidden email]
Labels: Type-Enhancement Priority-Medium GLASS-Server Version-1.0-beta.8.7

New issue 327 by [hidden email]: need to drop note in object log  
that there is important info in a gems log file
http://code.google.com/p/glassdb/issues/detail?id=327

I've known that in certain error conditions it is not possible for a vm to  
commit the entries to the object log and I've taken solace in the knowledge  
that at least the errors get logged to the gem log ... but that begs the  
question of when should one take a look at the gem log?

Perhaps we can arrange for a gem-to-gem signal to announce that errors have  
been logged to the gem log instead of the object log and arrange for  
another (healthy) gem to log some information to the object log ...