The good news: They aren't cached. The bad news: They're stored permanently.
The sogo_folder_info table in the database holds database connection information thrice for every user table (in c_location, c_quick_location and c_acl_location). You have to replace all to make them utilize the actual database. On 16.11.2011 15:32, a.roma...@gctrials.com wrote: > Hello everybody, > > After testing SOGo installation on the main server it was moved to the > deployment server. > Everything works fine, however there is one issue: > > When users that have logged on on the testing server log in, SOGo can't access > postgres. Configuration has been updated, and with new users logging in first > on the new server there is no problem. > > However with the users that logged in with previous settings I still see in > the > log it tries to open channel to localhost while it's not the database server > anymore, and all settings have been updated correspondingly (it WORKS for new > users). > > Are such settings cached user-specific? Where and how can I remove this cache? > > Thanks a lot! -- Mit freundlichen Grüßen, Sven SCHWEDAS Systemadministrator TAO Beratungs- und Management GmbH | Lendplatz 45 | A - 8020 Graz sven.schwe...@tao.at | +43 (0)664 820 4978 skype: sven.schwedas | xmpp: sven.schwe...@tao.at | www.tao.at
signature.asc
Description: OpenPGP digital signature
