Except the fact that the table logging has relative huge holes in it, and I do not know if it has something to do with the different moves.
However this does not really bother me, what bothers me more is that the ooo-wiki VM is so weak (compared to my notebook) that a lot of my "special" select/join statements timed out...and the just because I have a simple where clause "where user_id in (select user_id from wiki_maint_uids)" and that returns about 27.000 users :-) I have to change my scripts a bit, so I have subtables. Jan. On 29 November 2012 15:41, C <smau...@gmail.com> wrote: > On Thu, Nov 29, 2012 at 3:29 PM, Rob Weir <robw...@apache.org> wrote: > > On Thu, Nov 29, 2012 at 9:17 AM, janI <j...@apache.org> wrote: > >> Yes I locked it hard down, on request from the community....I had to use > >> the big knife to be fast. > >> > >> I am looking into how to open for sysop, but my concern is that at > least 2 > >> spam accounts (Or more correctly 2 that fit the pattern) have got > changed > >> rights and I cannot see to what...so either a sysop have done it, or > they > >> have somehow aquired sysop priviledges. > >> > > > > Third option: users with legacy sysop privileges had their accounts > > hacked due to weak passwords or something. > > While possible, admin-level changes leaves traces in the logs. You > are able to see who gave who admin rights and when. If the two > accounts in question have elevated rights at the regular user account > side, you can see this in > http://wiki.openoffice.org/wiki/Special:ListUsers (select > Administrators). I recognize all names there - there are no mystery > users. > > You can see who has done what related to user rights here: > http://wiki.openoffice.org/wiki/Special:Log/rights > > Removing single log entries is possible, but not from within the > browser - you need root level access to the database. > > Clayton >
